[SERVER-32168] Mongo shell crash after several days of uptime Created: 04/Dec/17  Updated: 22/Feb/18  Resolved: 29/Jan/18

Status: Closed
Project: Core Server
Component/s: Shell
Affects Version/s: 3.4.10
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Kaloian Manassiev Assignee: Mira Carey
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: Text File context.txt    
Issue Links:
Duplicate
duplicates SERVER-32683 Turn off the spidermonkey jit by default Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Participants:

 Description   

I had a shell connected to an Atlas cluster for a couple of days on my Mac OS laptop. When I eventually typed exit, it crashed with the stack trace below (I have also attached a fuller context). I haven't been able to reproduce it since.

 mongo(_ZN5mongo15printStackTraceERNSt3__113basic_ostreamIcNS0_11char_traitsIcEEEE+0x3A) [0x10f8f98fa]
 mongo(_ZN5mongo12_GLOBAL__N_124abruptQuitWithAddrSignalEiP9__siginfoPv+0x140) [0x10f8f9340]
 libsystem_platform.dylib(_sigtramp+0x1A) [0x7fff564edf5a]
 libsystem_c.dylib(__sfvwrite+0x173) [0x7fff562faa9f]
 mongo(_ZN2js2gc5Arena8finalizeI8JSObjectEEmPNS_6FreeOpENS0_9AllocKindEm+0x206) [0x10fe9cdd6]
 mongo(_ZL14FinalizeArenasPN2js6FreeOpEPPNS_2gc11ArenaHeaderERNS2_15SortedArenaListENS2_9AllocKindERNS_11SliceBudgetENS2_10ArenaLists14KeepArenasEnumE+0x136) [0x10fe80fb6]
 mongo(_ZN2js2gc10ArenaLists30queueForegroundObjectsForSweepEPNS_6FreeOpE+0x368) [0x10fe82f68]
 mongo(_ZN2js2gc9GCRuntime22beginSweepingZoneGroupEv+0xA82) [0x10fe89992]
 mongo(_ZN2js2gc9GCRuntime15beginSweepPhaseEb+0x20E) [0x10fe8aa9e]
 mongo(_ZN2js2gc9GCRuntime23incrementalCollectSliceERNS_11SliceBudgetEN2JS8gcreason6ReasonE+0x4C9) [0x10fe8d7a9]
 mongo(_ZN2js2gc9GCRuntime7gcCycleEbRNS_11SliceBudgetEN2JS8gcreason6ReasonE+0x191) [0x10fe8deb1]
 mongo(_ZN2js2gc9GCRuntime7collectEbNS_11SliceBudgetEN2JS8gcreason6ReasonE+0x1CF) [0x10fe8e4df]
 mongo(_ZN2js2gc9GCRuntime2gcE18JSGCInvocationKindN2JS8gcreason6ReasonE+0x65) [0x10fe8e965]
 mongo(_ZN2js14DestroyContextEP9JSContextNS_18DestroyContextModeE+0x18C) [0x10fe305ec]
 mongo(_ZN5mongo5mozjs14MozJSImplScope10MozRuntimeD2Ev+0x54) [0x10f7f1534]
 mongo(_ZN5mongo5mozjs14MozJSImplScopeD2Ev+0x1A31) [0x10f7e9f01]
 mongo(_ZN5mongo5mozjs14MozJSImplScopeD0Ev+0xE) [0x10f7eb93e]
 mongo(_ZN5mongo5mozjs15MozJSProxyScope10implThreadEPv+0x201) [0x10f81dbd1]
 mongo(_ZN4nspr6Thread13ThreadRoutineEPv+0x1C) [0x10f7d181c]
 mongo(_ZNSt3__114__thread_proxyINS_5tupleIJPFPvS2_EPN4nspr6ThreadEEEEEES2_S2_+0x61) [0x10f7d1de1]
 libsystem_pthread.dylib(_pthread_body+0x154) [0x7fff564f76c1]
 libsystem_pthread.dylib(_pthread_body+0x0) [0x7fff564f756d]
 libsystem_pthread.dylib(thread_start+0xD) [0x7fff564f6c5d]



 Comments   
Comment by Mira Carey [ 29/Jan/18 ]

I haven't seen crashes come out of js gc routines without the jit enabled, so closing this as a dup of that now that we're migrating that to off by default

Comment by Kaloian Manassiev [ 13/Dec/17 ]

All that I was doing prior to the crash is running finds and aggregations from the M121 course. And I was connected to the Atlas cluster from the examples as well.

If nothing stands out, feel free to close it, because I haven't been able to reproduce it since and don't have any core dumps or other leftovers.

Comment by Sara Golemon [ 13/Dec/17 ]

Thanks, the backtrace does give some clues and I'm hunting them down.
In the mean time, can you recall vaguely what you were up to in that client over that period?
Typical crud operations? Or anything less common like database copy. replSet init, shard rebalancing, etc... Just looking for any clues that might narrow the possibilties.

Thanks in advance!

Generated at Thu Feb 08 04:29:24 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.