Segmentation fault triggered inside tcmalloc, comments appreciated

[GoogleCodeExporter]

Here's a stack trace extracted from a core file using gdb:

#0  0xb7ad0a16 in tcmalloc::ThreadCache::ReleaseToCentralCache ()
   from /usr/lib/libtcmalloc.so.0
#1  0xb7ad0a6a in tcmalloc::ThreadCache::ListTooLong ()
   from /usr/lib/libtcmalloc.so.0
#2  0xb7adce00 in free () from /usr/lib/libtcmalloc.so.0
#3  0xb7d532e1 in operator delete () from /usr/lib/libstdc++.so.6
#4  0xb7d5333d in operator delete[] () from /usr/lib/libstdc++.so.6
#5  0x0808067a in OArray::~OArray ()
#6  0xb7975ab9 in exit () from /lib/i686/cmov/libc.so.6
#7  0x0808e46d in signal_segv (signum=11, info=0xb350fa9c, ptr=0xb350fb1c)
    at ../SourceCode/src/sigsegv.c:114
#8  <signal handler called>
#9  0xb7ad0a16 in tcmalloc::ThreadCache::ReleaseToCentralCache ()
   from /usr/lib/libtcmalloc.so.0
#10 0xb7ad0a6a in tcmalloc::ThreadCache::ListTooLong ()
   from /usr/lib/libtcmalloc.so.0
#11 0xb7adce00 in free () from /usr/lib/libtcmalloc.so.0

What is causing this to happen?

Original issue reported on code.google.com by donavanb...@gmail.com on 14 Apr 2009 at 8:46

[GoogleCodeExporter]

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

[GoogleCodeExporter]

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

• Changed state: CannotReproduce
• Added labels: Priority-Medium, Type-Defect