[SERVER-15634] ClientConnections::clearPool leaks ClientConnections::Status objects Created: 13/Oct/14 Updated: 03/Mar/15 Resolved: 16/Oct/14 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Internal Code |
| Affects Version/s: | None |
| Fix Version/s: | 2.7.8 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Andrew Morrow (Inactive) | Assignee: | Andrew Morrow (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | 28qa, address-sanitizer, leak-sanitizer, memory-leak | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Operating System: | ALL |
| Participants: |
| Description |
|
When ClientConnections::clearPool walks its _hosts lists, it deletes all of the DBClientBase objects held in each Status object, but does not delete the Status object itself. This is unlikely to be a real world issue since clearPool appears not to be used in normal operation, but does affect tests that invoke clearPool. |
| Comments |
| Comment by Githook User [ 16/Oct/14 ] |
|
Author: {u'username': u'acmorrow', u'name': u'Andrew Morrow', u'email': u'acm@mongodb.com'}Message: |