Fix stack-use-after-scope of TransactionParticipant in write_ops_exec::performAtomicTimeseriesWrites

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 5.0.0-rc0, 5.1.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Fully Compatible
    • ALL
    • v5.0
    • Execution Team 2021-05-31
    • 168
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      We currently use a reference to a TransactionParticipant that is on the stack inside of a storage transaction rollback handler. However, due to C++ destruction ordering, when we leave the frame this variable goes out of scope before the WriteUnitOfWork whose destructor causes the handler to run.

              Assignee:
              Gregory Noma
              Reporter:
              Gregory Noma
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: