This repository has been archived by the owner on Aug 8, 2023. It is now read-only.
[android] Do not try to wake up the RunLoop if a wake is already pending #15330
+12
−5
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.
Do not flood the RunLoop with wake up calls, potentially causing writes to the socket to block when internal pipe buffer goes over the limit defined by the system (usually 65536).
Also, write calls are syscalls and will cause a context switch.
Fixes #14740
/cc @alexshalamov that found the issue.