[SERVER-8697] src/third_party/gperftools-2.0/src/tcmalloc.cc:289] Attempt to free invalid pointer 0x7f5e000001ad Created: 25/Feb/13  Updated: 12/Mar/13  Resolved: 12/Mar/13

Status: Closed
Project: Core Server
Component/s: Stability
Affects Version/s: 2.2.0
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: nosqldb Assignee: Unassigned
Resolution: Cannot Reproduce Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

centos 6.2 final ,kernel 2.6.32


Attachments: File mongod.log.2013-02-23T16-01-01    
Operating System: Linux
Participants:

 Description   

...
src/third_party/gperftools-2.0/src/tcmalloc.cc:289] Attempt to free invalid pointer 0x7f5e000001ad
Sat Feb 23 03:33:13 Got signal: 6 (Aborted).
...
Sat Feb 23 03:33:14 Backtrace:
0xade6e1 0x5582d9 0x34a2e32900 0x34a2e32885 0x34a2e34065 0xa2138b 0x9ae503 0xc21716 0xaecb3c 0xb5d0ea 0x56fa52 0x5dbf11 0x34a32077f1 0x34a2ee570d
/export/servers/mongodb/bin/mongod(_ZN5mongo15printStackTraceERSo+0x21) [0xade6e1]
/export/servers/mongodb/bin/mongod(_ZN5mongo10abruptQuitEi+0x399) [0x5582d9]
/lib64/libc.so.6() [0x34a2e32900]
/lib64/libc.so.6(gsignal+0x35) [0x34a2e32885]
/lib64/libc.so.6(abort+0x175) [0x34a2e34065]
/export/servers/mongodb/bin/mongod(ZN8tcmalloc3LogENS_7LogModeEPKciNS_7LogItemES3_S3_S3+0x20b) [0xa2138b]
/export/servers/mongodb/bin/mongod() [0x9ae503]
/export/servers/mongodb/bin/mongod(free+0x36) [0xc21716]
/export/servers/mongodb/bin/mongod(_ZNK5mongo7OpDebug6reportERKNS_5CurOpE+0x11fc) [0xaecb3c]
/export/servers/mongodb/bin/mongod(_ZN5mongo16assembleResponseERNS_7MessageERNS_10DbResponseERKNS_11HostAndPortE+0x43a) [0xb5d0ea]
/export/servers/mongodb/bin/mongod(_ZN5mongo16MyMessageHandler7processERNS_7MessageEPNS_21AbstractMessagingPortEPNS_9LastErrorE+0x82) [0x56fa52]
/export/servers/mongodb/bin/mongod(_ZN5mongo3pms9threadRunEPNS_13MessagingPortE+0x411) [0x5dbf11]
/lib64/libpthread.so.0() [0x34a32077f1]
/lib64/libc.so.6(clone+0x6d) [0x34a2ee570d]



 Comments   
Comment by Andrew Morrow (Inactive) [ 12/Mar/13 ]

Closing per submitters request.

Comment by nosqldb [ 12/Mar/13 ]

hi Andrew Morrow,it's normal till now,and we'll upgrade to 2.2.3 . Could you please close the ticket,thank you!

Comment by Andrew Morrow (Inactive) [ 11/Mar/13 ]

Hi, I noticed that you set the status of this ticket back to 'open' without comment. Did you get a chance to upgrade to 2.2.3? Are you still running into issues? Let me know if there's anything else I can help you out with, otherwise we can mark this as closed. Thanks.

Comment by Andrew Morrow (Inactive) [ 08/Mar/13 ]

Looking at the stack trace you have provided here, and the one in SERVER-8698 which you also filed, these crashes look suspiciously like the result of memory corruption of some sort. I notice that you are running mongo 2.2.0. We have recently released version 2.2.3, which addresses some serious defects present in 2.2.0. We strongly recommend that you upgrade to version 2.2.3 as soon as possible and re-run your tests. If you continue to encounter this issue with 2.2.3 please update this ticket (and SERVER-8698 if you are able to reproduce that issue as well).

Going forward, filing tickets under the SERVER project is not the best way to get visibility for issues you encounter, as we use this project for tracking bugs and feature requests. If you have a support contract with 10gen, then filing commercial support tickets is your best option. If not, the 10gen development and support teams actively monitor posts to stackoverflow (http://stackoverflow.com/questions/tagged/mongodb) and to the mongo google group (https://groups.google.com/forum/?fromgroups#!forum/mongodb-user)

Comment by nosqldb [ 28/Feb/13 ]

Hi,James Wahlin,I attached the log,but it's hard to reproduce the problem.Thank you.

Comment by James Wahlin [ 27/Feb/13 ]

Can you provide:

  • The full mongod log
  • Steps to reproduce
Generated at Thu Feb 08 03:18:08 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.