| commit | c0c1497f999cea4d488ed334636b00b227fdca13 | [log] [tgz] |
|---|---|---|
| author | Derek Foreman <derekf@osg.samsung.com> | Fri Sep 11 14:30:39 2015 -0500 |
| committer | Bryce Harrington <bryce@osg.samsung.com> | Mon Sep 14 11:33:31 2015 -0700 |
| tree | e8e5f47eb6fa62d79234382a16061899f30a8024 | |
| parent | ca510d06dca3e47e434a50cee105e96c9e82599c [diff] |
shell: Make sure we actually have a resource in end_busy_cursor It's actually possible to get here after the surface has been destroyed, especially when running client apps under valgrind. That probably shouldn't be able to segfault the compositor. Signed-off-by: Derek Foreman <derekf@osg.samsung.com> Reviewed-by: Bryce Harrington <bryce@osg.samsung.com>