[SERVER-13162] Clean up _upsertDetails in ~BatchedCommandResponse() Created: 12/Mar/14 Updated: 11/Jul/16 Resolved: 12/Mar/14 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Write Ops |
| Affects Version/s: | 2.6.0-rc1 |
| Fix Version/s: | 2.6.0-rc2 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Siyuan Zhou | Assignee: | Siyuan Zhou |
| Resolution: | Done | Votes: | 0 |
| Labels: | 26qa | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Operating System: | ALL | ||||
| Participants: | |||||
| Description |
|
Vector _upsertDetails owns its members, so we should unset _upsertDetails in the deconstructor of BatchedCommandResponse. Otherwise it will cause a memory leak in BatchedCommandResponse::cloneTo(). |
| Comments |
| Comment by Githook User [ 12/Mar/14 ] |
|
Author: {u'username': u'visualzhou', u'name': u'Siyuan Zhou', u'email': u'siyuan.zhou@mongodb.com'}Message: |