[SERVER-3913] MongoDB 2.0 crashes on Windows 7 x64 Created: 20/Sep/11 Updated: 11/Jul/16 Resolved: 23/Sep/11 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Index Maintenance, Testing Infrastructure |
| Affects Version/s: | 2.0.0 |
| Fix Version/s: | 2.0.1, 2.1.0 |
| Type: | Bug | Priority: | Critical - P2 |
| Reporter: | Alexey Borzenkov | Assignee: | Sridhar Nanjundeswaran |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Windows 7 x64 |
||
| Attachments: |
|
||||||||||||
| Issue Links: |
|
||||||||||||
| Operating System: | Windows | ||||||||||||
| Participants: | |||||||||||||
| Description |
|
I have a big application that uses pymongo and when I tried out the new MongoDB 2.0 I found that MongoDB server crashes during tests (which are mostly complex integration/lifecycle tests with high concurrency). The crash is consistent is that it always happens during tests, but not always at the same test. This happens on my development Windows 7 x64 machine (with 64-bit MongoDB server), unfortunately I haven't had the time to test it on Linux (that is used in production), these crashes kind of halted the whole idea of an upgrade at the moment. I finally managed to look at it a little closer yesterday, and here's what gets written on the console at the time of the crash: Mon Sep 19 16:56:00 [initandlisten] connection accepted from 127.0.0.1:55254 #6 ntoreturn:1 reslen:70 339ms Mon Sep 19 16:56:01 [conn5] build index done 0 records 0.001 secs order: { files_id: 1, n: 1 }choices: { $natural: 1 }unhandled windows exMon Sep 19 16:56:01 access violation The warning is GridFS related, but I'm not sure how relevant it is. Unfortunately minidump doesn't really help, because I don't have .pdb files for the server, and the only exported symbols are pcre-related, so stack trace is pretty useless: 0:011> .ecxr
Is there a way to get pdb files for the build, or maybe some other way to help you figure out what's crashing so hard? |
| Comments |
| Comment by auto [ 23/Sep/11 ] |
|
Author: {u'login': u'erh', u'name': u'Eliot Horowitz', u'email': u'eliot@10gen.com'}Message: fix crash in filemd5 without correct index |
| Comment by auto [ 23/Sep/11 ] |
|
Author: {u'login': u'erh', u'name': u'Eliot Horowitz', u'email': u'eliot@10gen.com'}Message: fix crash in filemd5 without correct index |
| Comment by Sridhar Nanjundeswaran [ 22/Sep/11 ] |
|
When the attached script is executed against 1.8.3 it throws the error "best guess plan requested, but scan and order required: query: { files_id: 1.0 }order: { files_id: 1, n: 1 }choices: { $natural: 1 }". The database does not crash. |
| Comment by Sridhar Nanjundeswaran [ 20/Sep/11 ] |
|
Would you be able to send us the test suite you are using to cause this. Also what options are you using to start mongod on your local test environment. Finally what version of pymongo are you using |