Hi,

I am debugging a memory de-allocation issue. We are using jemalloc version 
3.5.1. It looks like a run with reg_size 224 and total size of 4 pages has 
"extended" into an adjacent run, and corrupted the adjacent run. Has such an 
issue been seen before ?


Thanks,

Chaitanya.
_______________________________________________
jemalloc-discuss mailing list
[email protected]
http://www.canonware.com/mailman/listinfo/jemalloc-discuss

Reply via email to