SERVER-135021ClosedFixed

Memory leak: OperationIdManager::IdPool::released lease list grows unboundedly — one list node retained per connection close, never recycled

h3. Summary OperationIdManager::IdPool hands out per-connection leases of OperationId ranges. On connection close, releaseLease() pushes the lease onto the released list (src/mongo/db/operation_id.cpp:75-77, :147). lease() consumes released *only* when exhaustedUniqueIds is true (:57-64) — i.e., when the 64-bit OperationId space is nearly exhausted, which never happens in practice. Therefore every connection close permanently retains one std::list node (≈40–48 B incl. allocator overhead). Gro

Affected Versions
Versions known to exhibit this issue
8.3.28.3.88.0.30
Fixed Versions
Versions that include the fix
9.1.0-rc09.1.0-rc1025
Components
Server components related to this issue
Networking
Labels
Tags and classification
memory-leaktcmalloc