shell: Make sure we actually have a resource in end_busy_cursor
authorDerek Foreman <derekf@osg.samsung.com>
Fri, 11 Sep 2015 19:30:39 +0000 (14:30 -0500)
committerBryce Harrington <bryce@osg.samsung.com>
Mon, 14 Sep 2015 18:33:31 +0000 (11:33 -0700)
commitc0c1497f999cea4d488ed334636b00b227fdca13
treee8e5f47eb6fa62d79234382a16061899f30a8024
parentca510d06dca3e47e434a50cee105e96c9e82599c
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>
desktop-shell/shell.c