[SERVER-5623] access violation in rollback4.js Created: 16/Apr/12 Updated: 15/Aug/12 Resolved: 30/Apr/12 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Ian Whalen (Inactive) | Assignee: | Eric Milkie |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | buildbot | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Windows 64-bit Weekly Slow Tests |
||
| Issue Links: |
|
||||||||
| Operating System: | ALL | ||||||||
| Participants: | |||||||||
| Description |
|
| Comments |
| Comment by Ian Whalen (Inactive) [ 25/Apr/12 ] |
|
Possibly related. http://buildbot.mongodb.org/builders/Windows%2064-bit%202008%2B/builds/286/steps/test_7/logs/stdio |
| Comment by Tad Marshall [ 21/Apr/12 ] |
|
Also, ASLR (Address Space Layout Randomization) makes the addresses hard to use effectively. The same crash address may appear as 0x00001230000 on one run and 0x00001290000 on the next run. Perhaps the access violation display code could display some "fixed" address as well so we could adjust offsets from one crash to another. |
| Comment by Eric Milkie [ 18/Apr/12 ] |
|
Possibly. We need to turn on minidumps (or at least stack backtracer) in order to efficiently diagnose these Windows issues that are intermittent. |
| Comment by Ian Whalen (Inactive) [ 18/Apr/12 ] |
|
Possibly related? http://buildbot.mongodb.org/builders/Windows%2064-bit%202008%2B/builds/271/steps/test_7/logs/stdio |