Large (reported) memory leak from fence-batched free changes
acomminos opened this issue · 1 comments
acomminos commented
Changes in the fence-batching frees are responsible for a memory leak. Look into this.
acomminos commented
Okay, this is comically straightforward to fix. An element in the free list was extraneously allocated, going unnoticed in the refactoring of element_insert_range
.
I'll update the patchset in an hour or so. Serves me right for writing patches late at night.