[PATCH weston v2 0/7] libweston: Make input object destruction safe
daniel at fooishbar.org
Tue Feb 13 12:07:08 UTC 2018
On 8 February 2018 at 13:37, Alexandros Frantzis
<alexandros.frantzis at collabora.com> wrote:
> When a weston seat or input object is destroyed, any associated client
> resources should become inert and put in a state in which they can
> safely handle client requests. Currently, client requests to such
> resources may lead to crashes and/or memory errors in the server.
> This patchset aims to fix (or at least greatly improve) the situation.
Thanks for finally taking care of this! I took a look yesterday
evening, and though I also can't speak authoritatively for the
desktop-shell changes, I looked enough to give the series:
Reviewed-by: Daniel Stone <daniels at collabora.com>
It would be good to get this in before the release, unless Quentin has
More information about the wayland-devel