wlr-protocols
wlr-protocols copied to clipboard
wlr_output_management is inherently racy
wlr_output_management as of d1598e82240d6e8ca57729495a94d4e11d222033 is inherently racy, as it has server-created objects that create more server-created objects. See https://gitlab.freedesktop.org/wayland/wayland/-/merge_requests/23#note_187475 for details.
This is a libwayland bug.
This is a libwayland bug.
The erroneous disconnect is certainly a libwayland bug, but I am not certain how best to ensure that all resources are cleaned up. Should libwayland-client automatically call destructors for objects created by requests to zombies? If so, this would require that the XML indicate doing so is safe.
wlr-protocols has migrated to gitlab.freedesktop.org. This issue has been moved to:
https://gitlab.freedesktop.org/wlroots/wlr-protocols/-/issues/108