[SERVER-2511] memory leak of _MultiCommandJob Created: 09/Feb/11 Updated: 12/Jul/16 Resolved: 17/Mar/11 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Stability |
| Affects Version/s: | None |
| Fix Version/s: | 1.9.0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Aaron Staple | Assignee: | Dwight Merriman |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Operating System: | ALL |
| Participants: |
| Description |
|
Unlike some BackgroundJob implementations, _MultiCommandJob isn't specified as selfDelete, so when we create a new _MultiCommandJob in multiCommand() it is never deleted. |
| Comments |
| Comment by Aaron Staple [ 17/Mar/11 ] |
|
Looks like the memory will get cleaned up with this patch. If it's ok to free the jobs after wait(), looks fine to me. |
| Comment by Dwight Merriman [ 17/Mar/11 ] |
|
@aaron look ok now? |
| Comment by auto [ 17/Mar/11 ] |
|
Author: {u'login': u'dwight', u'name': u'Dwight', u'email': u'dwight@10gen.com'}Message: |