[SERVER-9774] Random access exception accessing virtual memory on windows Created: 23/May/13 Updated: 10/Dec/14 Resolved: 20/Jun/14 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Stability |
| Affects Version/s: | 2.4.1, 2.4.3 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Chad Kreimendahl | Assignee: | Ramon Fernandez Marina |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | collector-298ba4e7 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Windows 8 |
||
| Attachments: |
|
||||||||
| Issue Links: |
|
||||||||
| Operating System: | Windows | ||||||||
| Participants: | |||||||||
| Description |
|
We've seen this happen in both 2.4.1 and 2.4.3 primarily in Windows 8 environments. Occasionally, following a set of queries, an access violation will cause mongod to exit and crash. Exception: "The thread tried to read from or write to a virtual address for which it does not have the appropriate access." (logs & dump attached) |
| Comments |
| Comment by Chad Kreimendahl [ 05/Feb/14 ] | |||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Part 2: our system.profile of the query in question:
| |||||||||||||||||||||||||||||||||||||||||||||||||||||
| Comment by Chad Kreimendahl [ 05/Feb/14 ] | |||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Part one of updating this... as we are still seeing it: Also, feel free to add windows 8.1 and server 2012 r2 to the environments list.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||
| Comment by Stennie Steneker (Inactive) [ 13/Aug/13 ] | |||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Hi Chad, We don't have enough information to be able to reproduce or progress this issue, so I'm going to close as Incomplete. If you are still seeing this exception with regular frequency, please feel free to reopen the issue with additional details. Regards, | |||||||||||||||||||||||||||||||||||||||||||||||||||||
| Comment by Tad Marshall [ 23/May/13 ] | |||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Hi Chad, The stack trace shows that a MapReduce job used a null pointer to read something (read from address 0). It is trying to use a "pooled" JavaScript "scope" which appears to be invalid. Can you post the MapReduce code that was running at the time of the crash? Tad |