-
Type: Bug
-
Resolution: Duplicate
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Storage, WiredTiger
-
None
-
Fully Compatible
-
ALL
-
(copied to CRM)
A user encountered a segfault when running MongoDB 3.0.14 on Windows Server 2012. The stack trace was:
2017-03-18T09:01:37.870-0400 I CONTROL *** unhandled exception (access violation) at 0x00007FF67BF5B552, terminating 2017-03-18T09:01:37.870-0400 I CONTROL *** access violation was a write to 0x00000000DEADBFFF 2017-03-18T09:01:37.870-0400 I CONTROL *** stack trace for unhandled exception: 2017-03-18T09:01:42.959-0400 I CONTROL mongod.exe ...\src\third_party\wiredtiger\src\evict\evict_lru.c(1385) __evict_get_ref+0x152 2017-03-18T09:01:42.959-0400 I CONTROL mongod.exe ...\src\third_party\wiredtiger\src\evict\evict_lru.c(1419) __wt_evict_lru_page+0x1c 2017-03-18T09:01:42.959-0400 I CONTROL mongod.exe ...\src\third_party\wiredtiger\src\evict\evict_lru.c(397) __evict_worker+0x40 2017-03-18T09:01:42.959-0400 I CONTROL MSVCR120.dll beginthreadex+0x107 2017-03-18T09:01:42.960-0400 I CONTROL MSVCR120.dll endthreadex+0x192 2017-03-18T09:01:42.960-0400 I CONTROL KERNEL32.DLL BaseThreadInitThunk+0x22 2017-03-18T09:01:42.960-0400 I - 2017-03-18T09:01:45.903-0400 I CONTROL *** immediate exit due to unhandled exception
The line of code that triggered the assertion was:
https://github.com/wiredtiger/wiredtiger/blob/mongodb-3.0/src/evict/evict_lru.c#L1385
It appears as though the application has a valid WT_REF, but the WT_BTREE has been freed. Our first step should be to search for bug fixes that match those characteristics in more recent versions of WiredTiger.
- depends on
-
WT-2321 WT-2321: race between eviction and worker threads on the eviction queue
- Closed