thread heap leak?

[Carlos O'Donell]

On 3/30/19 1:06 PM, David Muse wrote:
> 2aeb89a5e000-2aeb89a62000 rw-p 00000000 00:00 0	[16KiB]

> 2aeb89a62000-2aeb89a63000 ---p 00000000 00:00 0	[stack guard]
> 2aeb89a63000-2aeb89c63000 rw-p 00000000 00:00 0 - stack 1

> 2aeb89c63000-2aeb89c64000 ---p 00000000 00:00 0	[stack guard]
> 2aeb89c64000-2aeb89e64000 rw-p 00000000 00:00 0	[2MiB thread stack]

> 2aeb89e64000-2aeb89e65000 ---p 00000000 00:00 0	[stack guard]
> 2aeb89e65000-2aeb8a065000 rw-p 00000000 00:00 0 - stack 2

> 2aeb8c000000-2aeb8c097000 rw-p 00000000 00:00 0	[618KiB - heap, 64MiB + aligned]
> 2aeb8c097000-2aeb90000000 ---p 00000000 00:00 0	[66MiB - MADV_DONTNEED]

> 2aeb90000000-2aeb90093000 rw-p 00000000 00:00 0	[602KiB - heap, 64MiB + aligned]
> 2aeb90093000-2aeb94000000 ---p 00000000 00:00 0	[66MiB - MADV_DONTNEED]

> 2aeb94000000-2aeb940a2000 rw-p 00000000 00:00 0	[663KiB - heap, 64MiB + aligned]
> 2aeb940a2000-2aeb98000000 ---p 00000000 00:00 0	[66MiB - MADV_DONTNEED]
> 
> But what are the rest of those anonymous segments?
> 
> This might not be a thread-stack leak, but some other kind of leak.
> What else creates anonymous segments like that?

Looks like 3 threads, and 3 heaps.

-- 
Cheers,
Carlos.