Major - P3 Exposed by fixing SERVER-22950. When we return from mongoSMain, the UserCacheInvalidator is still running, but we have already destroyed its state, since it is created on the stack. This causes a segfault when it tries to access its members (such as its mutex).
race in destruction of user cache invalidation thread can cause use-after-free in MongoS shutdown
- Votes:
-
0 Vote for this issue
- Watchers:
-
3 Start watching this issue
- Created:
- Updated:
- Resolved: