Avoid referencing a potentially-destroyed future in collection_acquisition_bm

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 8.1.0-rc0, 8.0.0-rc11
    • Affects Version/s: None
    • Component/s: None
    • None
    • Service Arch
    • Fully Compatible
    • ALL
    • v8.0
    • Programmability 2024-05-27
    • 0
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      It's possible to try to get the _stopRequest future here after we already emplace the promise and destroy the future here.

      If we change the member ordering of _thread and _stopRequest it should solve the issue.

            Assignee:
            Blake Oler
            Reporter:
            Blake Oler
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: