One run extending into another in jemalloc-3.5.1 ?
cpatti at tintri.com
Tue Apr 19 11:26:35 PDT 2016
Let us say "run1" has extended into "run2". Are you saying that the metadata of run1 has been corrupted by a double free ?
> On Apr 19, 2016, at 10:01, Jason Evans <jasone at canonware.com> wrote:
>> On Apr 18, 2016, at 11:12 PM, Chaitanya Patti <cpatti at tintri.com> wrote:
>> 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 ?
> That usually means that a double free corrupted metadata for the adjacent run. If you have a repeatable test case, try running with a debug build of jemalloc, and disable tcache, so that assertions immediately detect double frees.
More information about the jemalloc-discuss