Closed GoogleCodeExporter closed 9 years ago
Almost always, this is due to application error: for instance, double-freeing a
pointer. If you can reduce this to a simple testcase, or otherwise debug this
a bit
further on your end, we can look into it more, but in my experience this is
unlikely
to be a bug in tcmalloc.
Original comment by csilv...@gmail.com
on 14 Apr 2009 at 7:21
I'm going to close this bug. Feel free to reopen if you determine it's a bug
within
tcmalloc.
Original comment by csilv...@gmail.com
on 18 Apr 2009 at 12:14
Original issue reported on code.google.com by
donavanb...@gmail.com
on 14 Apr 2009 at 8:46