-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fixes a potential deadlock; it's not safe to message likely super nod… #56
Fixes a potential deadlock; it's not safe to message likely super nod… #56
Conversation
4833258
to
a236df8
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Would it be simpler if we enumerate twice: first time to grab eventTargetActionArray
s with the lock held and second time to consume them without the lock?
@nguyenhuy That's a better idea, will update. |
@nguyenhuy hmmm, that actually increases the complexity of the code quite a bit. I need to keep 2 extra arrays around because responder could potentially be nil (so I can't use the original |
@garrettmoon Can we have a single array of |
a236df8
to
9fb1896
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
…es while holding the lock.