Investigate and fix memory tracking accuracy for $_internalSetWindowFields

XMLWordPrintableJSON

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

      1) The maxUsedMemBytes for $_internalSetWindowField is expected to be non-zero, but it is currently 0 for explain.

      2) $setWindowFields should clear memory on EOF. 

      We tried to force the current memory tally to go to zero by calling memoryTracker.resetCurrent() in setWindowField's doDispose() method, but that triggered an underflow in memory when testing a $setWindowFields when followed by a $limit that forced the $setWindowFields to return early.

       

       

              Assignee:
              Aaron Baruch
              Reporter:
              Erin Zhu
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: