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.
Fix stack-use-after-scope of TransactionParticipant in write_ops_exec::performAtomicTimeseriesWrites
- Votes:
-
0 Vote for this issue
- Watchers:
-
3 Start watching this issue
- Created:
- Updated:
- Resolved: