Assertion failed: (!pthread_mutex_destroy(&m)), function ~mutex, file /opt/local/include/boost/thread/pthread/mutex.hpp, line 45.
Wed Mar 3 01:41:06 Got signal: 6 (Abort trap).
Wed Mar 3 01:41:06 Backtrace:
0x57c13 0x17e423 0x91fa82bb 0xffffffff 0x15f4a1 0x18179d 0x1817c9 0x18752a 0x1bf6
0 mongod 0x00057c13 _ZN5mongo15printStackTraceERSo + 33
1 mongod 0x0017e423 _ZN5mongo10abruptQuitEi + 337
2 libSystem.B.dylib 0x91fa82bb _sigtramp + 43
3 ??? 0xffffffff 0x0 + 4294967295
4 mongod 0x0015f4a1 _ZN5mongo9sleepsecsEi + 45
5 mongod 0x0018179d _ZN5mongo14_initAndListenEiPKc + 1963
6 mongod 0x001817c9 _ZN5mongo13initAndListenEiPKc + 33
7 mongod 0x0018752a main + 23364
8 mongod 0x00001bf6 start + 54
Wed Mar 3 01:41:06 dbexit: ; exiting immediately

We allow mutexes to be held on shutdown, but boost doesn't like this. We've solved in the past by ensuring that boost mutexes that may be held at shutdown are never destroyed. We should use code to ensure that this the default whenever someone adds a new mutex.