[SERVER-26152] SEP interruptingSessionTest may clean up lambda before running it Created: 16/Sep/16  Updated: 19/Nov/16  Resolved: 30/Sep/16

Status: Closed
Project: Core Server
Component/s: Networking
Affects Version/s: None
Fix Version/s: 3.4.0-rc0

Type: Bug Priority: Major - P3
Reporter: Samantha Ritter (Inactive) Assignee: Samantha Ritter (Inactive)
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Platforms 2016-09-19, Platforms 2016-10-10
Participants:
Linked BF Score: 0

 Description   

This test assigns a lambda to a hook, then assigns something else to the hook before that lambda finishes running. As a result, on some platforms the disconnected lambda will have invalid pointers to its captured variables when it resumes running and will seg fault.



 Comments   
Comment by Githook User [ 30/Sep/16 ]

Author:

{u'username': u'samantharitter', u'name': u'samantharitter', u'email': u'samantha.ritter@10gen.com'}

Message: SERVER-26152 Do not reassign to _wait until lambda has fully run
Branch: master
https://github.com/mongodb/mongo/commit/1cc4ba9aeb1f6e76105d775bedbed968dae57ccc

Comment by Githook User [ 29/Sep/16 ]

Author:

{u'username': u'samantharitter', u'name': u'samantharitter', u'email': u'samantha.ritter@10gen.com'}

Message: Revert "SERVER-26152 Do not reassign to _wait until lambda has finished running"

This reverts commit b4d55086ed9a5d49709409c9c66652f12fa3d932.
Branch: master
https://github.com/mongodb/mongo/commit/4b6f1b99aea01016e875bb74872927b621c7321a

Comment by Githook User [ 29/Sep/16 ]

Author:

{u'username': u'samantharitter', u'name': u'Samantha Ritter', u'email': u'samantha.ritter@10gen.com'}

Message: SERVER-26152 Do not reassign to _wait until lambda has finished running
Branch: master
https://github.com/mongodb/mongo/commit/b4d55086ed9a5d49709409c9c66652f12fa3d932

Generated at Thu Feb 08 04:11:17 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.