[SERVER-9594] Occasional segfault in server Created: 06/May/13  Updated: 10/Dec/14  Resolved: 04/Apr/14

Status: Closed
Project: Core Server
Component/s: JavaScript
Affects Version/s: 2.2.2
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Ian Greenhoe Assignee: Unassigned
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Linux Centos 6.3


Issue Links:
Duplicate
is duplicated by SERVER-9595 Another occasional segfault in mongo ... Closed
Operating System: ALL
Steps To Reproduce:

Server under heavy load, with a complex M/R function.

I can't give more precise STR then that, unfortunately, as we have multiple complex M/R functions. When we have more precise information, we will attach it to this bug.

Participants:

 Description   

 Apr 26 05:21:20 localhost mongod.27017[2112]: Invalid access at address: 0 from thread: conn96
Apr 26 05:21:20 localhost mongod.27017[2112]: 
Apr 26 05:21:20 localhost mongod.27017[2112]: Fri Apr 26 05:21:20 
Apr 26 05:21:20 localhost mongod.27017[2112]: Got signal: 11 (Segmentation fault). 
Apr 26 05:21:20 localhost mongod.27017[2112]: 
Apr 26 05:21:21 localhost mongod.27017[2112]: Fri Apr 26 05:21:21 
Apr 26 05:21:21 localhost mongod.27017[2112]: Backtrace:
Apr 26 05:21:21 localhost /opt/bin/mongod(_ZN5mongo15printStackTraceERSo+0x26) [0x9ae416]
Apr 26 05:21:21 localhost /opt/bin/mongod(_ZN5mongo10abruptQuitEi+0x39d) [0x578f3d]
Apr 26 05:21:21 localhost /opt/bin/mongod(_ZN5mongo24abruptQuitWithAddrSignalEiP7siginfoPv+0x247) [0x5792a7]
Apr 26 05:21:21 localhost /opt/bin/mongod(JS_SetElement+0x13) [0x9fe833]
Apr 26 05:21:21 localhost /opt/bin/mongod(_ZN5mongo9Convertor5tovalERKNS_11BSONElementE+0x89f) [0x975e8f]
Apr 26 05:21:21 localhost /opt/bin/mongod(_ZN5mongo7SMScope4initEPKNS_7BSONObjE+0x110) [0x9763c0]
Apr 26 05:21:21 localhost /opt/bin/mongod(_ZN5mongo2mr5State4initEv+0x22e) [0x6790fe]
Apr 26 05:21:21 localhost /opt/bin/mongod(_ZN5mongo2mr16MapReduceCommand3runERKSsRNS_7BSONObjEiRSsRNS_14BSONObjBuilderEb+0x588) [0x6868f8]
Apr 26 05:21:21 localhost /opt/bin/mongod(_ZN5mongo12_execCommandEPNS_7CommandERKSsRNS_7BSONObjEiRNS_14BSONObjBuilderEb+0x4c) [0x6a125c]
Apr 26 05:21:21 localhost /opt/bin/mongod(_ZN5mongo11execCommandEPNS_7CommandERNS_6ClientEiPKcRNS_7BSONObjERNS_14BSONObjBuilderEb+0x7bb) [0x6a2c6b]
Apr 26 05:21:21 localhost /opt/bin/mongod(_ZN5mongo12_runCommandsEPKcRNS_7BSONObjERNS_11_BufBuilderINS_16TrivialAllocatorEEERNS_14BSONObjBuilderEbi+0x310) [0x6a3f30]
Apr 26 05:21:21 localhost /opt/bin/mongod(_ZN5mongo11runCommandsEPKcRNS_7BSONObjERNS_5CurOpERNS_11_BufBuilderINS_16TrivialAllocatorEEERNS_14BSONObjBuilderEbi+0x3a) [0x79a67a]
Apr 26 05:21:21 localhost /opt/bin/mongod(_ZN5mongo8runQueryERNS_7MessageERNS_12QueryMessageERNS_5CurOpES1_+0x87e) [0x7a00de]
Apr 26 05:21:21 localhost /opt/bin/mongod() [0x73a405]
Apr 26 05:21:21 localhost /opt/bin/mongod(_ZN5mongo16assembleResponseERNS_7MessageERNS_10DbResponseERKNS_11HostAndPortE+0x4a0) [0x73f780]
Apr 26 05:21:21 localhost /opt/bin/mongod(_ZN5mongo16MyMessageHandler7processERNS_7MessageEPNS_21AbstractMessagingPortEPNS_9LastErrorE+0xd9) [0x5904b9]
Apr 26 05:21:21 localhost /opt/bin/mongod(_ZN5mongo3pms9threadRunEPNS_13MessagingPortE+0x459) [0x99e329]
Apr 26 05:21:21 localhost mongod.27017[2112]: 



 Comments   
Comment by Ben Becker [ 07/May/13 ]

Thanks Ian. Memory consumption data would be very helpful. In the mean time, v2.4 may solve this issue due to the change in JavaScript implementations.

Comment by Ian Greenhoe [ 07/May/13 ]

Unfortunately, no memory tracking at the time.

OOM is a reasonable possibility.

I will see what I can do to track going forward.

Comment by Ben Becker [ 07/May/13 ]

Hi Ian,

We've seen similar issues with OOM conditions in SpiderMonkey. Do you have any data on memory utilization leading up to these events?

Generated at Thu Feb 08 03:20:53 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.