[SERVER-4383] Segfault [std::bad_alloc] Created: 29/Nov/11  Updated: 21/Jun/12  Resolved: 26/Jan/12

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

Type: Bug Priority: Minor - P4
Reporter: Ben Wyrosdick Assignee: Daniel Pasette (Inactive)
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Linux version 2.6.38-8-virtual (buildd@allspice) (gcc version 4.5.2 (Ubuntu/Linaro 4.5.2-8ubuntu3) ) #42-Ubuntu SMP Mon Apr 11 04:06:34 UTC 2011


Issue Links:
Depends
Operating System: Linux
Participants:

 Description   

We got a segfault and it isn't anything we are needing an answer on ... we just wanted to pass along in case it helps in debugging it for future release.

-------------------------------
– Below is the log snippet –
-------------------------------

Tue Nov 29 02:54:15 [conn98129182] Uncaught std::exception: std::bad_alloc, terminating
Tue Nov 29 02:54:15 dbexit:
Tue Nov 29 02:54:15 [conn98129182] shutdown: going to close listening sockets...
Tue Nov 29 02:54:15 [conn98129182] closing listening socket: 8
Tue Nov 29 02:54:15 [conn98129182] closing listening socket: 9
Tue Nov 29 02:54:15 [conn98129182] removing socket file: /tmp/mongodb-27017.sock
Tue Nov 29 02:54:15 [conn98129182] shutdown: going to flush diaglog...
Tue Nov 29 02:54:15 [conn98129182] shutdown: going to close sockets...
Tue Nov 29 02:54:15 [conn98129182] shutdown: waiting for fs preallocator...
Tue Nov 29 02:54:15 [conn98129182] shutdown: closing all files...
Tue Nov 29 02:54:15 [initandlisten] now exiting
Tue Nov 29 02:54:15 dbexit: ; exiting immediately
Tue Nov 29 02:54:15 Invalid access at address: 0x10000000f

Tue Nov 29 02:54:15 Got signal: 11 (Segmentation fault).

Tue Nov 29 02:54:15 Backtrace:
0x8ad399 0x8ad970 0x7f5fb47ddc60 0x7f5fb4534973 0x54665c 0x7566c8 0x756fa8 0x8aeced 0x7f5fb47d4d8c 0x7f5fb3d7f04d
/usr/local/bin/mongod(_ZN5mongo10abruptQuitEi+0x399) [0x8ad399]
/usr/local/bin/mongod(_ZN5mongo24abruptQuitWithAddrSignalEiP7siginfoPv+0x220) [0x8ad970]
/lib/x86_64-linux-gnu/libpthread.so.0(+0xfc60) [0x7f5fb47ddc60]
/usr/lib/x86_64-linux-gnu/libstdc++.so.6(_ZSt18_Rb_tree_incrementPSt18_Rb_tree_node_base+0x13) [0x7f5fb4534973]
/usr/local/bin/mongod(_ZN5mongo9MongoFile13closeAllFilesERSt18basic_stringstreamIcSt11char_traitsIcESaIcEE+0xac) [0x54665c]
/usr/local/bin/mongod(_ZN5mongo14shutdownServerEv+0x4b8) [0x7566c8]
/usr/local/bin/mongod(_ZN5mongo6dbexitENS_8ExitCodeEPKcb+0x258) [0x756fa8]
/usr/local/bin/mongod(_ZN5mongo10connThreadEPNS_13MessagingPortE+0xd2d) [0x8aeced]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x6d8c) [0x7f5fb47d4d8c]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x6d) [0x7f5fb3d7f04d]



 Comments   
Comment by Daniel Pasette (Inactive) [ 24/Dec/11 ]

Do you want to pursue this issue further? Is it for the same deployment as described in SERVER-4353?

Comment by Eliot Horowitz (Inactive) [ 29/Nov/11 ]

That means the process ran out of memory.
Hard to debug anything without full logs, etc...

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