This seems relevant:

m31000| Sat Apr 21 02:23:13 [conn2] *** unhandled exception (access violation) at 0x000000013FD52EFE, terminating
m31000| Sat Apr 21 02:23:13 [conn2] *** access violation was a read from 0x0000000009B80018

I tried to find the faulting code (hard because ASLR gives you 254 possible locations and we haven't added any code to allow us to adjust for this) and found one solid candidate: NamespaceDetailsTransient::notifyOfWriteOp() at line 537 in db/namespace_details.h.

/* you must notify the cache if you are doing writes, as query plan utility will change */
void notifyOfWriteOp()

I tried running the test on my home machine and was not able to duplicate the crash. It is possible that this is a compiler bug, broken in the original Visual Studio 2010 run by the Buildbot but fixed in the Service Pack 1 version running on my machine, but that is a guess and probably wishful thinking.

Author:

Message: LockMongoFilesExclusive in remapViewOfFiles on Windows.

Since remapViewOfFiles isn't atomic on Windows, it must exclusively acquire the
"mongo files" lock. Otherwise, "touch" operations in other threads might try
to access memory during the window when it is not mapped.

See SERVER-5680, SERVER-5663.
Branch: master
https://github.com/mongodb/mongo/commit/d8462a26b9089c5e58d1e340dcada83719ea4e47

This should be fixed by by Andy's addition of LockMongoFilesExclusive to remapPrivateView in Windows. Memory accesses to the private view being remapped would generate access violations if they happened during the window of time between the unmap and remap operations.

Unfortunately, this test failed again with the same access violation, even after Andy's change was introduced.

It's odd to me how it's this one particular test that keeps hitting an accvio, on the same line of code. I'm going to attempt to flush it out running in the debugger.

Running in debug mode, repl13.js hits an assert on startup:

 m31000| Mon Apr 30 12:03:39 [journal]   Assertion failure s <= 0 e:\m\mongo\src\mongo\db\../util/concurrency/rwlock.h 175

 m31000| Mon Apr 30 12:03:39 [journal] *** unhandled exception 0x80000003 at 0x000007FEFD6E3172, terminating

 m31000| Mon Apr 30 12:03:39 [journal] writing minidump dignostic file 0000000140C38BD0

Author:

Message: SERVER-5680 fix Windows accvios due to incorrect recursive locking of MongoFiles
Branch: master
https://github.com/mongodb/mongo/commit/8b099a96ac9b5a1f73954204806ef8e0c77d481a

Note that this should fix the test failures from the slow weekly builders as well. I looked at their dump files and rollback4.js is crashing in the same place (rec->touch()).

Author:

Message: SERVER-5680 fix Windows accvios due to incorrect recursive locking of MongoFiles

Conflicts:
db/dur.cpp
Branch: v2.0
https://github.com/mongodb/mongo/commit/c88805a6f6447458290719703887fb736692359e