Out-of-order destruction of AutoGet* objects can lead to transaction closure

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 5.0.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Fully Compatible
    • ALL
    • Query Execution 2021-04-19
    • 166
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      Steps to reproduce:

      1. AutoGetCollectionForReadMaybeLockFree number one is created
      2. AutoGetCollectionForReadMaybeLockFree number two is created
      3. We destroy the first object
      4. Deep underneath this object holds GlobalLock, which thinks it is outermost, since it was created first
      5. GlobalLock calls abandonSnapshot(), closing transaction and reseting the cursors

            Assignee:
            Mihai Andrei
            Reporter:
            Nikita Lapkov (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated:
              Resolved: