[SERVER-2323] new seg fault in evalc.js (curop) - in small oplog tests Created: 03/Jan/11  Updated: 12/Jul/16  Resolved: 05/Jan/11

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

Type: Bug Priority: Major - P3
Reporter: Aaron Staple Assignee: Aaron Staple
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Operating System: ALL
Participants:

 Description   

Let me know if you want me to investigate...

<http://buildbot.mongodb.org/builders/Linux%2032-bit/builds/2605/steps/test_5/logs/stdio>

Mon Jan 3 16:36:18 [conn3] getmore local.oplog.$main cid:1172252514751192584 getMore: { ts:

{ $gte: new Date(5558076263895138309) }

} bytes:20 nreturned:0 3566ms
Mon Jan 3 16:36:20 Got signal: 11 (Segmentation fault).

Mon Jan 3 16:36:20 Backtrace:
0x8510852 0xbe1420 0x2dd4bc 0x83b63ac 0x83adfe7 0x83b10bf 0x8513c04 0x81f4f58 0x852826d 0xefe542 0x340b6e
/mnt/slaves/Linux_32bit/mongo/mongod(_ZN5mongo10abruptQuitEi+0x3c2) [0x8510852]
[0xbe1420]
/lib/i686/nosegneg/libc.so.6(memcpy+0x1c) [0x2dd4bc]
/mnt/slaves/Linux_32bit/mongo/mongod(_ZN5mongo5CurOp10infoNoauthEv+0x5ec) [0x83b63ac]
/mnt/slaves/Linux_32bit/mongo/mongod(_ZN5mongo9inProgCmdERNS_7MessageERNS_10DbResponseE+0x367) [0x83adfe7]
/mnt/slaves/Linux_32bit/mongo/mongod(_ZN5mongo16assembleResponseERNS_7MessageERNS_10DbResponseERKNS_8SockAddrE+0x17af) [0x83b10bf]
/mnt/slaves/Linux_32bit/mongo/mongod(_ZN5mongo10connThreadEPNS_13MessagingPortE+0x214) [0x8513c04]
/mnt/slaves/Linux_32bit/mongo/mongod(_ZN5boost6detail11thread_dataINS_3_bi6bind_tIvPFvPN5mongo13MessagingPortEENS2_5list1INS2_5valueIS6_EEEEEEE3runEv+0x18) [0x81f4f58]
/mnt/slaves/Linux_32bit/mongo/mongod(thread_proxy+0x7d) [0x852826d]
/lib/i686/nosegneg/libpthread.so.0 [0xefe542]
/lib/i686/nosegneg/libc.so.6(clone+0x5e) [0x340b6e]



 Comments   
Comment by Aaron Staple [ 05/Jan/11 ]

I didn't reproduce this exact failure, but I think the commit above is at least relevant to what happened. I'm going to resolve the jira, but we can reopen if it happens again or if you want me to try harder to reproduce.

Comment by auto [ 04/Jan/11 ]

Author:

{u'login': u'astaple', u'name': u'Aaron', u'email': u'aaron@10gen.com'}

Message: SERVER-2323 CachedBSONObj::reset() minor cleanup
https://github.com/mongodb/mongo/commit/24655afe33c64f387d8b2664d88e980d47e92bfe

Comment by auto [ 04/Jan/11 ]

Author:

{u'login': u'astaple', u'name': u'Aaron', u'email': u'aaron@10gen.com'}

Message: SERVER-2323 make CachedBSONObj::reset() thread safe
https://github.com/mongodb/mongo/commit/8b99193220a126f07dea62964b2f222984fa944c

Comment by Eliot Horowitz (Inactive) [ 03/Jan/11 ]

Yes please.

Generated at Thu Feb 08 02:59:37 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.