backend: use distinct event queue for client sys #738
Merged
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
|
might also fix #728 |
elinorbgr
reviewed
Jun 24, 2024
some drivers seem to unconditionally dispatch the default event queue. this can lead to spurious dispatching of wayland-rs managed objects breaking the tls invariant. prevent this from happening by moving everything off the default event queue to a distinct event queue
cmeissl
force-pushed
the
fix/driver_dispatch_crash
branch
from
8816be2
to
a00b771
Compare
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.
some drivers seem to unconditionally dispatch
the default event queue. this can lead to spurious dispatching of wayland-rs managed objects breaking the tls invariant.
prevent this from happening by moving everything
off the default event queue to a distinct event queue