If getThreadName() is invoked before ThreadContextsInitialized is complete, a SIGSEGV will happen. The name is typically needed for debugging and logging purposes and should not cause a crash. This ticket is to implement a mitigation to SIGSEGV
- is related to
-
SERVER-64639 Stitch SDK hits invariant initializing ThreadContext
-
- Closed
-
-
-
- Closed
-
-
SERVER-66385 Remove ThreadName's dependence on ThreadContext (& vice versa apparently)
-
- Closed
-
- split to
-
-
- Closed
-