[SERVER-9065] Replicable segfault while storing or accessing documents Created: 21/Mar/13  Updated: 10/Dec/14  Resolved: 21/Mar/13

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

Type: Bug Priority: Blocker - P1
Reporter: Abhas Abhinav Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Ubuntu 13.04


Issue Links:
Duplicate
duplicates SERVER-8799 Sort or Find on Symbol data type thro... Closed
Operating System: Linux
Participants:

 Description   

I'm using Ruby 1.9.3 with Mongoid 2.6.0 to connect to Mongoid 2.4.0. Today when I'm trying to insert embedded documents or list them, MongoDB gives me a replicable segfault each time I try to do so. I tried to do this with a nightly build of mongodb as well but get the same result each time.

(mongod-2.4.0)>db.documents.find()
Fri Mar 22 01:39:03.788 Assertion: 16661:can't handle type: 14 status: "new"
0x747301 0x7106bb 0x710bfc 0x6ee1dc 0x6f3c3b 0x990843 0x990223 0x9ed1e0 0xe02aa506362
mongo(_ZN5mongo15printStackTraceERSo+0x21) [0x747301]
mongo(_ZN5mongo11msgassertedEiPKc+0x9b) [0x7106bb]
mongo() [0x710bfc]
mongo(_ZN5mongo7V8Scope16mongoToV8ElementERKNS_11BSONElementEb+0x48c) [0x6ee1dc]
mongo() [0x6f3c3b]
mongo(_ZN2v88internal8JSObject35GetPropertyAttributeWithInterceptorEPS1_PNS0_6StringEb+0x453) [0x990843]
mongo(_ZN2v88internal10JSReceiver32GetPropertyAttributeWithReceiverEPS1_PNS0_6StringE+0xb3) [0x990223]
mongo(_ZN2v88internal19Runtime_HasPropertyENS0_9ArgumentsEPNS0_7IsolateE+0x70) [0x9ed1e0]
[0xe02aa506362]
Fri Mar 22 01:39:03.793 mongo got signal 11 (Segmentation fault), stack trace:

Fri Mar 22 01:39:03.799 0x747301 0x5dc542 0x7f91326050b0 0x9fe232 0x895046 0x7f371f 0x6f3c58 0x990843 0x990223 0x9ed1e0 0xe02aa506362
mongo(_ZN5mongo15printStackTraceERSo+0x21) [0x747301]
mongo(_Z12quitAbruptlyi+0x382) [0x5dc542]
/lib/x86_64-linux-gnu/libc.so.6(+0x370b0) [0x7f91326050b0]
mongo(_ZN2v88internal7Runtime22ForceSetObjectPropertyEPNS0_7IsolateENS0_6HandleINS0_8JSObjectEEENS4_INS0_6ObjectEEES8_18PropertyAttributes+0x302) [0x9fe232]
mongo(_ZN2v88internal16ForceSetPropertyENS0_6HandleINS0_8JSObjectEEENS1_INS0_6ObjectEEES5_18PropertyAttributes+0x66) [0x895046]
mongo(_ZN2v86Object8ForceSetENS_6HandleINS_5ValueEEES3_NS_17PropertyAttributeE+0xef) [0x7f371f]
mongo() [0x6f3c58]
mongo(_ZN2v88internal8JSObject35GetPropertyAttributeWithInterceptorEPS1_PNS0_6StringEb+0x453) [0x990843]
mongo(_ZN2v88internal10JSReceiver32GetPropertyAttributeWithReceiverEPS1_PNS0_6StringE+0xb3) [0x990223]
mongo(_ZN2v88internal19Runtime_HasPropertyENS0_9ArgumentsEPNS0_7IsolateE+0x70) [0x9ed1e0]
[0xe02aa506362]



 Comments   
Comment by Ben Becker [ 21/Mar/13 ]

Thanks for the report. This issue has been fixed in the v2.5 branch, and is a candidate for backport to v2.4.1. Please see SERVER-8799 for details.

Comment by Andy Schwerin [ 21/Mar/13 ]

Actually, the stack trace definitely comes from the mogno shell. Looks like the V8 adapter is having trouble with the Symbol BSON type (14). Might also be possible to reproduce in a MR or $where in the server.

Comment by Andy Schwerin [ 21/Mar/13 ]

To clarify, is the shell crashing or the mongo server? The stack trace you supplied comes either from the shell, or from a map reduce, or from a $where or $group clause using javascript.

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