Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-15632

MultiHostQueryOp::PendingQueryContext::doBlockingQuery can leak a cursor object

    • Fully Compatible
    • ALL

      In MultiHostQueryOp::PendingQueryContext::doBlockingQuery , the result of calling doBlockingQuery is only noted, causing an ownership transfer, if the parent op still exists.

      In the case where the parentOp no longer exists after doBlockingQuery, the DBClientCursor object is not freed.

            Assignee:
            andrew.morrow@mongodb.com Andrew Morrow (Inactive)
            Reporter:
            andrew.morrow@mongodb.com Andrew Morrow (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: