This repository has been archived by the owner on Nov 1, 2021. It is now read-only.
wlr_output_management is inherently racy #108
Comments
|
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 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
wlr_output_management as of d1598e8 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.
The text was updated successfully, but these errors were encountered: