There is a MongoDB test case called:
storage_wiredtiger_prefixed_record_store_test.exe
It fails with an assertion:
file:a.b.wt, WT_SESSION.checkpoint: __wt_checkpoint_get_handles, 317: !metadata_race
The stack trace is:
...\src\mongo\util\stacktrace_windows.cpp(239) mongo::printStackTrace+0x43 ...\src\mongo\util\signal_handlers_synchronous.cpp(182) mongo::`anonymous namespace'::printSignalAndBacktrace+0x73 ...\src\mongo\util\signal_handlers_synchronous.cpp(238) mongo::`anonymous namespace'::abruptQuit+0x83 d:\th\minkernel\crts\ucrt\src\appcrt\misc\signal.cpp(522) raise+0x468 d:\th\minkernel\crts\ucrt\src\appcrt\startup\abort.cpp(71) abort+0x39 ...\src\third_party\wiredtiger\src\os_common\os_abort.c(31) __wt_abort+0x15 ...\src\third_party\wiredtiger\src\support\err.c(504) __wt_assert+0x37 ...\src\third_party\wiredtiger\src\txn\txn_ckpt.c(325) __wt_checkpoint_get_handles+0x1fe ...\src\third_party\wiredtiger\src\conn\conn_dhandle.c(517) __conn_btree_apply_internal+0x97 ...\src\third_party\wiredtiger\src\conn\conn_dhandle.c(574) __wt_conn_btree_apply+0x2e6 ...\src\third_party\wiredtiger\src\txn\txn_ckpt.c(190) __checkpoint_apply_all+0x270 ...\src\third_party\wiredtiger\src\txn\txn_ckpt.c(681) __checkpoint_prepare+0x30d ...\src\third_party\wiredtiger\src\txn\txn_ckpt.c(791) __txn_checkpoint+0x243 ...\src\third_party\wiredtiger\src\txn\txn_ckpt.c(985) __txn_checkpoint_wrapper+0x62 ...\src\third_party\wiredtiger\src\txn\txn_ckpt.c(1038) __wt_txn_checkpoint+0xac ...\src\third_party\wiredtiger\src\session\session_api.c(1680) __session_checkpoint+0x149 ...\src\mongo\db\storage\wiredtiger\wiredtiger_session_cache.cpp(265) mongo::WiredTigerSessionCache::waitUntilDurable+0x3de ...\src\mongo\db\storage\wiredtiger\wiredtiger_kv_engine.cpp(174) mongo::WiredTigerKVEngine::WiredTigerCheckpointThread::run+0x470
The failure has only been seen on Windows, but I have no reason to believe the failure mode is Windows specific.