[SERVER-14747] memory leak in the MultiPlanStage Created: 31/Jul/14  Updated: 16/Jan/15  Resolved: 01/Aug/14

Status: Closed
Project: Core Server
Component/s: Querying
Affects Version/s: 2.7.4
Fix Version/s: 2.7.5

Type: Bug Priority: Major - P3
Reporter: David Storch Assignee: David Storch
Resolution: Done Votes: 0
Labels: cap-ticket-needed
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to SERVER-16889 Query subsystem public API should use... Closed
Tested
Backwards Compatibility: Fully Compatible
Operating System: ALL
Steps To Reproduce:

Run the following and watch the memory usage using a tool like "top":

t.drop();
t.ensureIndex({a: 1, b: 1});
t.ensureIndex({a: 1, c: 1});
t.insert({a: 1});
for (var i = 0; i < 100000; i++) { t.find({a: 1}).explain(true); }

Participants:

 Description   

The MultiPlanStage deletes all pointers which it owns, except for the QuerySolution for the winning plan. The MultiPlanStage should either keep ownership of all QuerySolutions, or transfer ownership of the winning solution to the PlanExecutor.

This issue affects 2.7 versions only, and does not affect any production releases.



 Comments   
Comment by Githook User [ 02/Nov/14 ]

Author:

{u'username': u'acmorrow', u'name': u'Andrew Morrow', u'email': u'acm@mongodb.com'}

Message: SERVER-14747 SERVER-14753 Add validation tests for memory leak fixes
Branch: master
https://github.com/mongodb/mongo/commit/9eb7ba71ac9f3d056b7b1f41e384a9bb732078c0

Comment by Githook User [ 01/Aug/14 ]

Author:

{u'username': u'dstorch', u'name': u'David Storch', u'email': u'david.storch@10gen.com'}

Message: SERVER-14747 fix memory leak in MultiPlanStage
Branch: master
https://github.com/mongodb/mongo/commit/383282d628b1738ab801f57f20dbab3648104073

Generated at Thu Feb 08 03:35:51 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.