Re: [Valgrind-developers] stacks for new threads leaking?

[Nicholas N. <nj...@ca...>]

On Sun, 27 Jun 2004, Nicholas Nethercote wrote:

> do__apply_in_new_thread() allocates a new thread stack if the old one isn't 
> big enough, via VG_(mmap)().
>
> cleanup_after_thread_exited() doesn't free the stack, although it looks like 
> the place where that should be happening.
>
> It's possible that the stacks are intended to be kept around so that if the 
> thread is reused later the stack can be reused too.  But in that case, when 
> do__apply_in_new_thread() allocates the new one, the old one should be freed.
>
> So I think there's a leak here.  Does that sound right?

Hmm, it looks like Tom's commit earlier today for the thread attribute 
stuff fixed this.  Sorry for the noise.

N