QuerySolutionNode not safely managed in all code paths

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 3.5.8
    • Affects Version/s: None
    • Component/s: Querying
    • None
    • Fully Compatible
    • ALL
    • Query 2017-05-29
    • 0
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      ASAN is showing that the CollectionScanNode created by makeCollectionScan is getting leaked. There are a few paths that do not explicitly delete this object:

      1) The MatchExpression shallowClone operation just after the CollectionScanNode creation can throw an exception.

      2) At least one error path in QueryPlannerAnalysis::analyzeDataAccess() exits early without freeing the "solnRoot" QuerySolutionNode object.

              Assignee:
              Justin Seyster
              Reporter:
              Justin Seyster
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: