fix(pannel): offload ddcutil initialization to background thread to f… - #558
Open
ayush213 wants to merge 1 commit into
Open
fix(pannel): offload ddcutil initialization to background thread to f…#558ayush213 wants to merge 1 commit into
ayush213 wants to merge 1 commit into
Conversation
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Problem:
During the initialization of the Wayfire panel widget, MCCS operations and device enumeration via ddcutil are executed synchronously on the main thread. Because querying external monitors through ddcutil involves noticeable I/O latency, this blocks the main thread and introduces significant startup lag and unresponsiveness when launching the panel.
Solution:
Offloaded blocking ddcutil initialisation and MCCS device enumeration tasks away from the main thread into a background thread.
Ensured that panel startup remains fast, smooth, and fully responsive by avoiding synchronous blocking calls during component initialization.
Closes #555