[SERVER-6481] Invalid write to a deleted ClientCursor after yield recovery fails Created: 17/Jul/12 Updated: 11/Jul/16 Resolved: 17/Jul/12 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Stability |
| Affects Version/s: | None |
| Fix Version/s: | 2.2.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Aaron Staple | Assignee: | Eliot Horowitz (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Operating System: | ALL | ||||||||||||
| Participants: | |||||||||||||
| Description |
|
There are a couple of places doing something like the following:
If res if false, the 'this' pointer will have been deleted so calling _yieldSometimesTracker.resetLastTime() causes a write to invalid memory. I believe the resulting memory corruption causes |
| Comments |
| Comment by Aaron Staple [ 17/Jul/12 ] |
|
@eliot - looks good |
| Comment by Eliot Horowitz (Inactive) [ 17/Jul/12 ] |
|
@aaron - can you take a quick look at commit |
| Comment by auto [ 17/Jul/12 ] |
|
Author: {u'date': u'2012-07-16T22:27:32-07:00', u'email': u'eliot@10gen.com', u'name': u'Eliot Horowitz'}Message: |