Something is seriously wrong with --disable-munmap (default on linux)
jasone at canonware.com
Wed May 9 15:00:11 PDT 2012
On May 9, 2012, at 11:21 AM, Jason Evans wrote:
> On May 9, 2012, at 6:32 AM, Mike Hommey wrote:
>> Something is seriously wrong with --disable-munmap. What I see in
>> Firefox is that it seems free chunks are never reused, or seldomly: I
>> end up with a process sucking gigabytes of mapped memory, while jemalloc
>> claims it mapped 500M. On 32-bits system, that exhausts the address
> I saw the same thing yesterday on a 64-bit system, though the application was at 729 GiB of virtual memory use and climbing… I'm looking into this problem more today.
I found and fixed two problems, one of which was Windows-specific:
This likely fixes all the virtual memory leaks, but more testing is warranted.
More information about the jemalloc-discuss