[SERVER-11731] $where inside of projection $elemMatch causes segmentation fault Created: 15/Nov/13 Updated: 11/Jul/16 Resolved: 09/Dec/13 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | JavaScript |
| Affects Version/s: | 2.4.8 |
| Fix Version/s: | 2.2.7, 2.4.9 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Luke Lovett | Assignee: | Matt Dannenberg |
| Resolution: | Done | Votes: | 0 |
| Labels: | 26qa, nqf | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
> db.serverBuildInfo() { "version" : "2.4.8", "gitVersion" : "a350fc38922fbda2cec8d5dd842237b904eafc14", "sysInfo" : "Darwin bs-osx-106-x86-64-2.10gen.cc 10.8.0 Darwin Kernel Version 10.8.0: Tue Jun 7 16:32:41 PDT 2011; root:xnu-1504.15.3~1/RELEASE_X86_64 x86_64 BOOST_LIB_VERSION=1_49", "loaderFlags" : "-fPIC -pthread -rdynamic -m64", "compilerFlags" : "-Wnon-virtual-dtor -Woverloaded-virtual -fPIC -fno-strict-aliasing -ggdb -pthread -Wall -Wsign-compare -Wno-unknown-pragmas -Winvalid-pch -O3 -m64", "allocator" : "system", "versionArray" : [ 2, 4, 8, 0 ], "javascriptEngine" : "V8", "bits" : 64, "debug" : false, "maxBsonObjectSize" : 16777216, "ok" : 1 } |
||
| Attachments: |
|
||||||||||||
| Issue Links: |
|
||||||||||||
| Operating System: | ALL | ||||||||||||
| Steps To Reproduce: | 1. Start mongod 2.4.8
|
||||||||||||
| Participants: | |||||||||||||
| Description |
|
Issue Status as of December 30th, 2013 ISSUE SUMMARY USER IMPACT
SOLUTION
WORKAROUNDS PATCHES problem: mongod 2.4.8 crashes with a segmentation fault when doing a $where inside of a $elemMatch. This appears to be fixed in versions 2.5.x. mongod log attached |
| Comments |
| Comment by Githook User [ 09/Dec/13 ] |
|
Author: {u'username': u'dannenberg', u'name': u'matt dannenberg', u'email': u'matt.dannenberg@10gen.com'}Message: |
| Comment by Githook User [ 09/Dec/13 ] |
|
Author: {u'username': u'dannenberg', u'name': u'matt dannenberg', u'email': u'matt.dannenberg@10gen.com'}Message: |