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

VoteRequestor and FreshnessChecker need safe destruction

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • None
    • 3.5.13
    • Replication
    • Fully Compatible
    • ALL
    • Repl 2017-07-31, Repl 2017-08-21, Repl 2017-09-11
    • 15

    Description

      The VoteRequester and FreshnessChecker can be destroyed with callbacks still pending on their ScatterGatherRunner. Since the callbacks access the ScatterGatherRunner::Algorithm owned by the VoteRequestor/FreshnesssChecker, this can result in various bad behavior (crashes or memory corruption leading to just about anything). The ScatterGatherRunner::Algorithm needs to live until all callbacks are complete.

      This would probably make sense to combine with SERVER-28389

      Attachments

        Issue Links

          Activity

            People

              siyuan.zhou@mongodb.com Siyuan Zhou
              matthew.russotto@mongodb.com Matthew Russotto
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: