memory and cursor leak in FindingStartCursor

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Done
    • Priority: Major - P3
    • 1.8.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • ALL
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      It looks like in many cases where createClientCursor is called, the old _findingStartCursor is orphaned rather than freed.

      Also, it might be nice to ensure the FindingStartCursor destructor cleans up _findingStartCursor so we won't orphan the cursor in case of killop.

              Assignee:
              Aaron Staple (Inactive)
              Reporter:
              Aaron Staple (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

                Created:
                Updated:
                Resolved: