Files
weston/libweston
Pekka Paalanen dcbcfc7f67 libweston: cancel idle_repaint on output destroy
If the idle_repaint() callback has been scheduled when a weston_output
gets destroyed, the callback will hit use-after-free. I have encountered
this when migrating the wayland backend to the head-based API, using
--sprawl, and closing/disconnecting one of the parent compositor
outputs.

Store the idle_repaint callback source, and destroy it in
weston_output_release(), ensuring we don't get a stale call to
start_repaint_loop later.

Signed-off-by: Pekka Paalanen <pekka.paalanen@collabora.co.uk>
Reviewed-by: Ian Ray <ian.ray@ge.com>
Reviewed-by: Daniel Stone <daniels@collabora.com>
Acked-by: Derek Foreman <derekf@osg.samsung.com>
2018-04-17 15:19:57 +03:00
..
2016-07-26 16:26:08 -07:00
2016-06-23 17:44:54 +03:00
2016-06-23 17:44:54 +03:00
2016-06-23 17:44:54 +03:00
2016-06-23 17:44:54 +03:00
2016-06-23 17:44:54 +03:00
2016-06-23 17:44:54 +03:00
2016-06-23 17:44:54 +03:00
2016-06-23 17:44:54 +03:00
2016-06-23 17:44:54 +03:00
2016-06-23 17:44:54 +03:00
2016-06-23 17:44:54 +03:00
2016-06-23 17:44:54 +03:00
2016-06-23 17:44:54 +03:00