[SERVER-30688] Using multiple changeStream cursors causes a segfault Created: 16/Aug/17 Updated: 30/Oct/23 Resolved: 17/Aug/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | 3.5.11 |
| Fix Version/s: | 3.5.12 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Ross Lawley | Assignee: | Matthew Russotto |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Operating System: | ALL | ||||||||
| Steps To Reproduce: | Open the shell and call next() on two changeStream cursors. Code example in the description. |
||||||||
| Sprint: | Repl 2017-08-21 | ||||||||
| Participants: | |||||||||
| Description |
|
When running on 3.5.11 or nightly the following code run in the shell causes the primary node to segfault.
(If testing on 3.5.11 change the aggregation to be $changeNotification). |
| Comments |
| Comment by Githook User [ 17/Aug/17 ] |
|
Author: {'username': 'mtrussotto', 'email': 'matthew.russotto@10gen.com', 'name': 'Matthew Russotto'}Message: |
| Comment by Matthew Russotto [ 16/Aug/17 ] |
|
This is caused by doing an awaitData query on the auxiliary (fullDocument) lookup. |