Fix collision between iterator and throw-away argument to XQueryPointer() #38
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
…er() Without this, Openbox is unstable on any setup with more than 2 X screens, as the collision can make the loop infinitely call XQueryPointer() on X screen 1.
|
@danakj , Can we please get this change merged. This will improve the multi X-screen support on openbox |
|
The crux of this issue is that if the cursor goes onto an X screen >= 2 (the third X screen), Openbox will freeze and X will begin consuming 100% CPU as a result of Openbox being stuck in a loop repeatedly calling XQueryPointer() |
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.
Without this, Openbox is unstable on any setup with more than 2 X screens, as the collision can make the loop infinitely call XQueryPointer() on X screen 1.