-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Major - P3
-
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.
- related to
-
SERVER-105637 Add an assertion that the in-use bytes are zero in the MemoryTracker destructor
-
- Closed
-