[haiku-3rdparty-dev] Re: Memory leack while spawning & resuming threads (Haiku-Alpha 3)
- From: Robert Stiehler <r.stiehler85@xxxxxxxxxxxxxx>
- To: haiku-3rdparty-dev@xxxxxxxxxxxxx
- Date: Fri, 9 Sep 2011 22:06:47 +0200
Hi,
this classes and methods handle/accepting socket connections. But anyway
they could not be related to the problem, because if they are the problem,
the memory leak would exist with and without the spawned and resumed thread.
regards,
Robert
2011/9/9 Rene Gollent <anevilyak@xxxxxxxxx>
> On Fri, Sep 9, 2011 at 3:35 PM, Robert Stiehler
> <r.stiehler85@xxxxxxxxxxxxxx> wrote:
> > mAcceptor.accept(*stream);
>
> What is mAcceptor and what is its accept() call actually doing? There
> are any number of places where this code could be leaking inside of
> the member functions being called here (accept(), close(), CSockStream
> d'tor, etc.), but without seeing them that's not really something that
> can be accurately evaluated. It's highly unlikely
> spawn_thread/resume_thread have such a bug in any case, or you'd see
> that behavior universally across all teams.
>
> Regards,
>
> Rene
>
>
Other related posts:
