Transfer ownership of memory tracker on cursor timeout

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Fixed
    • Priority: Major - P3
    • 8.2.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Query Integration
    • Fully Compatible
    • 0
    • None
    • 3
    • TBD
    • None
    • None
    • None
    • None
    • None
    • None

      https://jira.mongodb.org/browse/BF-37637 caught a situation where a missing opCtx tassert was triggered on a disposal of a subpipeline that contains a memory-tracked stage. The pipeline disposal was triggered by a cursor timeout and is similar in spirit to the killCursors issue described in https://jira.mongodb.org/browse/SERVER-103337, so we just need to do what we did in that ticket to fix this BF.

            Assignee:
            Erin Liang
            Reporter:
            Erin Liang
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: