Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-74427

Refactor lifetime of OplogCapMaintainerThread

    XMLWordPrintableJSON

Details

    • Icon: Improvement Improvement
    • Resolution: Fixed
    • Icon: Major - P3 Major - P3
    • 7.0.0-rc0
    • None
    • None
    • Fully Compatible
    • Execution Team 2023-03-20, Execution Team 2023-04-03, Execution Team 2023-04-17

    Description

      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.

      Attachments

        Activity

          People

            jordi.olivares-provencio@mongodb.com Jordi Olivares Provencio
            jordi.olivares-provencio@mongodb.com Jordi Olivares Provencio
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: