[SERVER-21760] C runtime crash in the mongo shell due to uninitialized variable 'machine' Created: 03/Dec/15 Updated: 08/Jan/24 Resolved: 06/May/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Shell |
| Affects Version/s: | 3.2.0-rc6 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Kaloian Manassiev | Assignee: | Mira Carey |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Operating System: | Windows |
| Steps To Reproduce: | E:\workspace\mongo>mongo.exe --nodb |
| Sprint: | Platforms E (01/08/16), Platforms 10 (02/19/16) |
| Participants: |
| Description |
|
Pressing tab for completion in the shell, multiple times in a row in quick succession causes the crash below on Windows (haven't tried on Linux). The shell was started with the --nodb flag.
Stack:
|
| Comments |
| Comment by Mira Carey [ 06/May/16 ] |
|
No longer seems reproducible under mozjs-45. Closing as gone away |
| Comment by Mira Carey [ 03/May/16 ] |
|
Can you still repro this using mozjs-45? I.e. latest master? |
| Comment by Mira Carey [ 09/Feb/16 ] |
|
Ah, that's interesting. I thought it was debug only. What does a retail crash look like (does it still show up out of the crt, or does it segfault or something like that?) |
| Comment by Kaloian Manassiev [ 09/Feb/16 ] |
|
Just for the record, it also happened on retail build previously, so it is not related to debug. Probably now because I was doing it through remote session from home, I was not able to press the tab completion key fast enough |
| Comment by Mira Carey [ 09/Feb/16 ] |
|
In the short term, you can use --disableJavaScriptJIT to avoid that behavior on debug builds. In the long term, I'm going to have to work with Mark to trace the callstack back through jitted frames to find out where we went wrong, and there's always the chance that the debug build is just broken (it's definitely broken on non-x86) |
| Comment by Kelsey Schubert [ 03/Dec/15 ] |
|
I haven't been able to reproduce this on Linux or OS X. |