-
-
Notifications
You must be signed in to change notification settings - Fork 15.8k
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
Fix a race condition in DefaultPromise #2186
Closed
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
.. which occurs when a user adds a listener from different threads after the promise is done and the notifications for the listeners, that were added before the promise is done, is in progress. For instance: Thread-1: p.addListener(listenerA); Thread-1: p.setSuccess(null); Thread-2: p.addListener(listenerB); Thread-2: p.executor.execute(taskNotifyListenerB); Thread-1: p.executor.execute(taskNotifyListenerA); taskNotifyListenerB should not really notify listenerB until taskNotifyListenerA is finished. To fix this issue, a new volatile flag 'listenersNotified' were added. 'listenersNotified' is set once all listeners added before the promise is done are notified. If 'listenersNotified' is not set, the notifications for the listeners added after the promise is done will be rescheduled for later execution.
|
As you noticed, this didn't work out. Thinking of a proper fix. |
With c97f2d2, the test did not fail with 20000000 runs. I'd say it's fixed really. |
@trustin looks good... Please squash and cherry-pick or should I take care for you so you can get some sleep ;) ? |
Merged via 309ee68. Thanks for reviewing @normanmaurer |
pulllock
pushed a commit
to pulllock/netty
that referenced
this pull request
Oct 19, 2023
…n notifed. Part of [netty#2186]. This regression was introduced by commit c97f2d2
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
.. which occurs when a user adds a listener from different threads after the promise is done and the notifications for the listeners, that were added before the promise is done, is in progress. For instance:
taskNotifyListenerB should not really notify listenerB until taskNotifyListenerA is finished.
To fix this issue:
[1] the listeners that were added before the promise is done
[2] the listeners that were added after the promise is done