Details
-
Improvement
-
Resolution: Done
-
Major - P3
-
2.2.0
-
None
-
Fully Compatible
Description
Currently, background threads like ReplicaSetMonitorWatcher are not being cleaned up properly when an application using a replica set connection terminates, often resulting with an ugly stack trace.
Attachments
Issue Links
- is depended on by
-
SERVER-10843 example tutorial (valgrind memleak checkable ) memory leak
-
- Closed
-
- is duplicated by
-
CXX-99 Require driver users to runGlobalInitializersOrDie
-
- Closed
-
- related to
-
SERVER-6922 ReplicaSetMonitor should clean itself up (after stopping ReplicaSetMonitorWatcher) while program terminates
-
- Closed
-
-
SERVER-6217 BackgroundJobs cannot be run multiple times
-
- Closed
-
-
CXX-99 Require driver users to runGlobalInitializersOrDie
-
- Closed
-