Configuring jemalloc with --enable-munmap made valgrind error messages
vanish! No more error messages as far as I could test.
Are there any disadvantages of using --enable-munmap? I see that it
enables virtual memory deallocation via munmap. It seens that it was
enabled by default in previous version of jemalloc. Is that correct?
Will you change this VALGRIND_MAKE_MEM_UNDEFINED() call in
chunk_recycle() so that configuring jemalloc with --enable-munmap won't
be in future versions?
best regards,
Daniel Mezzatto
On 12/12/2012 03:32 PM, Jason Evans wrote:
Ah, this info narrows things down a bit. Can you try configuring jemalloc with
--enable-munmap and see if the problem persists? It seems probable that the
VALGRIND_MAKE_MEM_UNDEFINED() call in chunk_recycle() should be unconditional.
_______________________________________________
jemalloc-discuss mailing list
[email protected]
http://www.canonware.com/mailman/listinfo/jemalloc-discuss
