Right now the thread gets spawned with a raw new and the pointer goes out of scope without ever being {{delete}}d.
This is a literal memory leak that's harmless since it should only ever be deleted during shutdown. Nonetheless, we could refactor the code so at least it's lifetime is tied to the service context via a unique_ptr.
- related to
-
SERVER-90643 oplog reference may be invalidated in OplogCapMaintainer loop
-
- Closed
-