Fix wallpaper lifecycle, resource usage, and benchmark reliability - #2
Merged
Merged
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.
Fix wallpaper lifecycle failures that could leave playback blank, repeat conversions, retain lock-feed buffers after unlock, or send asynchronous replies to the wrong client. Preserve pause policy across lock transitions, keep media replacement responsive, and release Wayland and QML resources on failure and disconnect.
Share bounded IPC handling between the daemon and renderer, reduce lock-feed readback and copying, reuse EGL contexts and unchanged textures, clean abandoned cache files, and make benchmarks verify playback and restore the original state. Recover from system-bus disconnects, ship the QML plugin, and add regression coverage for the affected behavior.
Reviewed by Claude Fable 5.1