mongo shell crashes on exit

[p.perroud@…]

I have installed mongodb 2.4.8 port on Mavericks.

When I quit mongo shell with a Ctrl-D after a full bench a db queries fired from the command line, the shell simply crashes on exit with signal 11 error ("Segmentation fault"):

mongo
MongoDB shell version: 2.4.8
connecting to: test
> use test_unit
switched to db test_unit
> db.tu.find().pretty()
{
	[ . . . ]
}
Type "it" for more
> 

[ ctrl+D ]

bye
Mon Nov  4 15:14:02.065 mongo got signal 11 (Segmentation fault: 11), stack trace: 

Mon Nov  4 15:14:02.215 0x10430da2a 0x10420da2a 0x7fff8fec55aa 0xa 0x10438d6c7 0x10445acc9 0x10445ab31 0x1042cb4ad 0x1042cb35f 0x1042149ab 0x104214fbf 0x7fff8908b5fd 
 0   mongo                               0x000000010430da2a _ZN5mongo15printStackTraceERNSt3__113basic_ostreamIcNS0_11char_traitsIcEEEE + 58
 1   mongo                               0x000000010420da2a _Z12quitAbruptlyi + 666
 2   libsystem_platform.dylib            0x00007fff8fec55aa _sigtramp + 26
 3   ???                                 0x000000000000000a 0x0 + 10
 4   mongo                               0x000000010438d6c7 _ZN2v88internal15DeoptimizerDataD1Ev + 55
 5   mongo                               0x000000010445acc9 _ZN2v88internal7Isolate6DeinitEv + 105
 6   mongo                               0x000000010445ab31 _ZN2v88internal7Isolate8TearDownEv + 81
 7   mongo                               0x00000001042cb4ad _ZN5mongo7V8ScopeD2Ev + 285
 8   mongo                               0x00000001042cb35f _ZN5mongo7V8ScopeD0Ev + 15
 9   mongo                               0x00000001042149ab _Z5_mainiPPcS0_ + 22507
 10  mongo                               0x0000000104214fbf main + 95
 11  libdyld.dylib                       0x00007fff8908b5fd start + 1


bye
Mon Nov  4 17:49:39.573 mongo got signal 11 (Segmentation fault: 11), stack trace: 

Mon Nov  4 17:49:39.575 0x10c757a2a 0x10c657a2a 0x7fff8fec55aa 0xa 0x10c7d76c7 0x10c8a4cc9 0x10c8a4b31 0x10c7154ad 0x10c71535f 0x10c65e9ab 0x10c65efbf 0x7fff8908b5fd 0x2 
 0   mongo                               0x000000010c757a2a _ZN5mongo15printStackTraceERNSt3__113basic_ostreamIcNS0_11char_traitsIcEEEE + 58
 1   mongo                               0x000000010c657a2a _Z12quitAbruptlyi + 666
 2   libsystem_platform.dylib            0x00007fff8fec55aa _sigtramp + 26
 3   ???                                 0x000000000000000a 0x0 + 10
 4   mongo                               0x000000010c7d76c7 _ZN2v88internal15DeoptimizerDataD1Ev + 55
 5   mongo                               0x000000010c8a4cc9 _ZN2v88internal7Isolate6DeinitEv + 105
 6   mongo                               0x000000010c8a4b31 _ZN2v88internal7Isolate8TearDownEv + 81
 7   mongo                               0x000000010c7154ad _ZN5mongo7V8ScopeD2Ev + 285
 8   mongo                               0x000000010c71535f _ZN5mongo7V8ScopeD0Ev + 15
 9   mongo                               0x000000010c65e9ab _Z5_mainiPPcS0_ + 22507
 10  mongo                               0x000000010c65efbf main + 95
 11  libdyld.dylib                       0x00007fff8908b5fd start + 1
 12  ???                                 0x0000000000000002 0x0 + 2

bye
Mon Nov  4 20:09:02.678 mongo got signal 11 (Segmentation fault: 11), stack trace: 

Mon Nov  4 20:09:02.728 0x103a6ba2a 0x10396ba2a 0x7fff8fec55aa 0xa 0x103aeb6c7 0x103bb8cc9 0x103bb8b31 0x103a294ad 0x103a2935f 0x1039729ab 0x103972fbf 0x7fff8908b5fd 
 0   mongo                               0x0000000103a6ba2a _ZN5mongo15printStackTraceERNSt3__113basic_ostreamIcNS0_11char_traitsIcEEEE + 58
 1   mongo                               0x000000010396ba2a _Z12quitAbruptlyi + 666
 2   libsystem_platform.dylib            0x00007fff8fec55aa _sigtramp + 26
 3   ???                                 0x000000000000000a 0x0 + 10
 4   mongo                               0x0000000103aeb6c7 _ZN2v88internal15DeoptimizerDataD1Ev + 55
 5   mongo                               0x0000000103bb8cc9 _ZN2v88internal7Isolate6DeinitEv + 105
 6   mongo                               0x0000000103bb8b31 _ZN2v88internal7Isolate8TearDownEv + 81
 7   mongo                               0x0000000103a294ad _ZN5mongo7V8ScopeD2Ev + 285
 8   mongo                               0x0000000103a2935f _ZN5mongo7V8ScopeD0Ev + 15
 9   mongo                               0x00000001039729ab _Z5_mainiPPcS0_ + 22507
 10  mongo                               0x0000000103972fbf main + 95
 11  libdyld.dylib                       0x00007fff8908b5fd start + 1

[ryandesign (Ryan Carsten Schmidt)]

Have you followed the migration instructions to properly reinstall Xcode, its command line tools, MacPorts and all its ports after upgrading to Mavericks? If you have, then this is a mongodb bug that should be reported to its developers.

[p.perroud@…]

Replying to ryandesign@…:

Have you followed the migration instructions to properly reinstall Xcode, its command line tools, MacPorts and all its ports after upgrading to Mavericks? If you have, then this is a mongodb bug that should be reported to its developers.

I confirm I am using XCode 5.0.1 and its late October Mavericks CLT: I doubt any port would compile if I had not.

I have re-installed macports entirely so I am not really migrating from 10.8. It' not only about mongodb: dozens of ports have compiled fine on Mavericks. I have only met very few glitches so far - mostly the mongodb 2.4.7 issue...

I would be glad to report this crashing issue to mongodb myself but don't know howto: please provide a pointer to their bug tracking if you want me to do so.

[ryandesign (Ryan Carsten Schmidt)]

Thanks for confirming. We've had many reports from users who experienced problems with some but not all ports because they either didn't upgrade Xcode or the command line tools or because they didn't reinstall MacPorts or rebuild all ports, so I'm asking these questions on most Mavericks tickets. But if the problem occurs on a clean and properly-configured system like yours then reporting the problem to the developers is probably a good idea. Their issue tracker is here: ​https://jira.mongodb.org

[p.perroud@…]

You will notice that V8 seems to be involved in the 3 reported crash cases (each one starting on "bye"): could that be another v8 issue? V8 being Google's Javascript engine the mongo shell is built upon...

[ryandesign (Ryan Carsten Schmidt)]

If it's a v8 issue, I'd still report it to the developers of mongodb, because mongodb uses its own internal copy of v8, so if it has a problem, the mongodb developers need to fix it or update it.

[p.perroud@…]

Replying to ryandesign@…:

If it's a v8 issue, I'd still report it to the developers of mongodb, because mongodb uses its own internal copy of v8, so if it has a problem, the mongodb developers need to fix it or update it.

Done: ​https://jira.mongodb.org/browse/SERVER-11570

[p.perroud@…]

Got a response from MongoDB: ​https://jira.mongodb.org/browse/SERVER-11570.

In short this was a clang issue in V8 they fixed in their 2.5 branch. Since 2.4.8 is using the same V8 code this is the same bug they have fixed in 2.5.3. Since they don't backport fixes, they won't be able to address it in 2.4.8. They are suggesting this could be addressed on macports side. To me this raise once again the need for a 2.5 -devel port...

[ryandesign (Ryan Carsten Schmidt)]

Thanks. I'll look into back porting that fix to 2.4 and including it in our mongodb port.

[hapaguy (Brian Kurt Fujikawa)]

Cc Me!

[ryandesign (Ryan Carsten Schmidt)]

Replying to ryandesign@…:

I'll look into back porting that fix to 2.4 and including it in our mongodb port.

r113011