This is the mail archive of the
mailing list for the glibc project.
Re: thread heap leak?
- From: Florian Weimer <fw at deneb dot enyo dot de>
- To: David Muse <david dot muse at firstworks dot com>
- Cc: Andreas Schwab <schwab at suse dot de>, "Carlos O'Donell" <codonell at redhat dot com>, libc-alpha at sourceware dot org
- Date: Sat, 27 Apr 2019 11:35:34 +0200
- Subject: Re: thread heap leak?
- References: <email@example.com> <firstname.lastname@example.org> <email@example.com> <firstname.lastname@example.org> <email@example.com> <firstname.lastname@example.org> <email@example.com> <firstname.lastname@example.org> <email@example.com> <firstname.lastname@example.org>
* David Muse:
> I can correlate call number 6 and calls numbered 10-27 with the
> process map. Presumedly, 1-5 and 7-9 were unmapped. 10-27 appear to
> be thread stacks, considering their size, and that they were called
> with the MAP_STACK option :)
The other regions appear to be 64 MiB heaps created by malloc, with
some regions not backed by storage. There should be at least one such
heap for each thread. They will be reused for new threads eventually.