[SERVER-11899] Invalid access at address: 0x10 from thread: conn1 Created: 29/Nov/13  Updated: 11/Jul/16  Resolved: 19/Mar/14

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

Type: Bug Priority: Major - P3
Reporter: Roman [X] Assignee: Unassigned
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-11099 clang compiled mongo shell crashes on... Closed
Operating System: OS X
Steps To Reproduce:

Not sure, it's after multiple connection from PHP

Participants:

 Description   
          • SERVER RESTARTED *****

Fri Nov 29 14:09:16.491 [initandlisten] MongoDB starting : pid=61373 port=27017 dbpath=/usr/local/var/mongodb 64-bit host=Roman-Mac-mini.local
Fri Nov 29 14:09:16.491 [initandlisten] db version v2.4.8
Fri Nov 29 14:09:16.491 [initandlisten] git version: nogitversion
Fri Nov 29 14:09:16.491 [initandlisten] build info: Darwin Roman-Mac-mini.local 13.0.0 Darwin Kernel Version 13.0.0: Thu Sep 19 22:22:27 PDT 2013; root:xnu-2422.1.72~6/RELEASE_X86_64 x86_64 BOOST_LIB_VERSION=1_49
Fri Nov 29 14:09:16.491 [initandlisten] allocator: tcmalloc
Fri Nov 29 14:09:16.491 [initandlisten] options:

{ bind_ip: "127.0.0.1", command: [ "run" ], config: "/usr/local/etc/mongod.conf", dbpath: "/usr/local/var/mongodb", logappend: "true", logpath: "/usr/local/var/log/mongodb/mongo.log" }

Fri Nov 29 14:09:16.492 [initandlisten] journal dir=/usr/local/var/mongodb/journal
Fri Nov 29 14:09:16.492 [initandlisten] recover begin
Fri Nov 29 14:09:16.493 [initandlisten] recover lsn: 0
Fri Nov 29 14:09:16.493 [initandlisten] recover /usr/local/var/mongodb/journal/j._0
Fri Nov 29 14:09:16.496 [initandlisten] recover cleaning up
Fri Nov 29 14:09:16.496 [initandlisten] removeJournalFiles
Fri Nov 29 14:09:16.496 [initandlisten] recover done
Fri Nov 29 14:09:16.516 [websvr] admin web console waiting for connections on port 28017
Fri Nov 29 14:09:16.517 [initandlisten] waiting for connections on port 27017
Fri Nov 29 14:09:30.956 [initandlisten] connection accepted from 127.0.0.1:63033 #1 (1 connection now open)
Fri Nov 29 14:09:30.961 [initandlisten] connection accepted from 127.0.0.1:63035 #2 (2 connections now open)
Fri Nov 29 14:09:31.259 [initandlisten] connection accepted from 127.0.0.1:63039 #3 (3 connections now open)
Fri Nov 29 14:09:52.145 Invalid access at address: 0x10 from thread: conn1

Fri Nov 29 14:09:52.145 Got signal: 11 (Segmentation fault: 11).

Fri Nov 29 14:09:52.151 Backtrace:
0x1099fd9e0 0x10950e27d 0x10950e5b8 0x7fff95e815aa 0x109c4eb96 0x109b30097 0x109bfd699 0x109bfd501 0x1099b75cb 0x1099b748f 0x1099b236a 0x1099b17cf 0x1096a74d4 0x1096a78cc 0x109687055 0x109688013 0x109688df6 0x10979d04d 0x1097a3468 0x10974092a
0 mongod 0x00000001099fd9e0 _ZN5mongo15printStackTraceERSo + 64
1 mongod 0x000000010950e27d _ZN5mongo10abruptQuitEi + 397
2 mongod 0x000000010950e5b8 ZN5mongo24abruptQuitWithAddrSignalEiP9_siginfoPv + 344
3 libsystem_platform.dylib 0x00007fff95e815aa _sigtramp + 26
4 mongod 0x0000000109c4eb96 _ZN2v88internal10JSReceiver25GetLocalPropertyAttributeEPNS0_6StringE + 454
5 mongod 0x0000000109b30097 _ZN2v88internal15DeoptimizerDataD1Ev + 55
6 mongod 0x0000000109bfd699 _ZN2v88internal7Isolate6DeinitEv + 105
7 mongod 0x0000000109bfd501 _ZN2v88internal7Isolate8TearDownEv + 81
8 mongod 0x00000001099b75cb _ZN5mongo7V8ScopeD2Ev + 267
9 mongod 0x00000001099b748f _ZN5mongo7V8ScopeD0Ev + 15
10 mongod 0x00000001099b236a _ZN5mongo11PooledScopeD2Ev + 842
11 mongod 0x00000001099b17cf _ZN5mongo11PooledScopeD0Ev + 15
12 mongod 0x00000001096a74d4 _ZN5mongo6dbEvalERKSsRNS_7BSONObjERNS_14BSONObjBuilderERSs + 1812
13 mongod 0x00000001096a78cc _ZN5mongo7CmdEval3runERKSsRNS_7BSONObjEiRSsRNS_14BSONObjBuilderEb + 172
14 mongod 0x0000000109687055 _ZN5mongo12_execCommandEPNS_7CommandERKSsRNS_7BSONObjEiRSsRNS_14BSONObjBuilderEb + 37
15 mongod 0x0000000109688013 _ZN5mongo7Command11execCommandEPS0_RNS_6ClientEiPKcRNS_7BSONObjERNS_14BSONObjBuilderEb + 2915
16 mongod 0x0000000109688df6 _ZN5mongo12_runCommandsEPKcRNS_7BSONObjERNS_11_BufBuilderINS_16TrivialAllocatorEEERNS_14BSONObjBuilderEbi + 886
17 mongod 0x000000010979d04d _ZN5mongo11runCommandsEPKcRNS_7BSONObjERNS_5CurOpERNS_11_BufBuilderINS_16TrivialAllocatorEEERNS_14BSONObjBuilderEbi + 45
18 mongod 0x00000001097a3468 ZN5mongo8runQueryERNS_7MessageERNS_12QueryMessageERNS_5CurOpES1 + 1112
19 mongod 0x000000010974092a _ZN5mongo16assembleResponseERNS_7MessageERNS_10DbResponseERKNS_11HostAndPortE + 1338



 Comments   
Comment by Richard Kreuter (Inactive) [ 16/Dec/13 ]

Hi Roman,

It seems the fix for this V8 issue has been backported to the 2.4 branch. So the next 2.4 release, version 2.4.9, should contain this fix. Version 2.4.9 is slated for release early January of next year.

As an alternative workaround, the binaries available at

http://www.mongodb.org/downloads

should not have ever evinced this defect, since they are compiled with GCC instead of clang.

Regards,
Richard

Comment by Roman [X] [ 30/Nov/13 ]

Confirm that, it's same error and Mongo was installed with homebrew

Meanwhile mongo devel version (2.5.4) seem to be stable installed same way as previous version.

Comment by Andrew Morrow (Inactive) [ 30/Nov/13 ]

Based on the stack trace, this looks like you are encountering SERVER-11099. Can you confirm that you built mongodb with clang, or obtained it from an upstream package that was built with clang (i.e. macports or homebrew)?

If so, your workaround is to either recompile with GCC rather than clang, or to incorporate the patch identified in SERVER-11099 in your build process (I believe MacPorts already does this). Our current position is that we do not plan to backport the fix for SERVER-11099 to 2.4 since clang support was not a release goal for 2.4.

Comment by Scott Hernandez (Inactive) [ 29/Nov/13 ]

What is the javascript you are running? Please attach it.

Comment by Roman [X] [ 29/Nov/13 ]

Yes, it's RockMongo and using db.eval

Comment by Scott Hernandez (Inactive) [ 29/Nov/13 ]

Are you using db.eval() in your code? If so, what is the javascript code?

Has this happened more than once, or was this an isolated incident?

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