Re: [PATCH weston] shell: Make sure we actually have a resource in end_busy_cursor

2015-09-15 Thread Bryce Harrington
On Mon, Sep 14, 2015 at 11:32:44AM -0700, Bryce Harrington wrote: > On Fri, Sep 11, 2015 at 02:30:39PM -0500, Derek Foreman wrote: > > 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

Re: [PATCH weston] shell: Make sure we actually have a resource in end_busy_cursor

2015-09-14 Thread Bryce Harrington
On Fri, Sep 11, 2015 at 02:30:39PM -0500, Derek Foreman wrote: > 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 Accord

[PATCH weston] shell: Make sure we actually have a resource in end_busy_cursor

2015-09-11 Thread Derek Foreman
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 --- desktop-shell/shell.c | 1 + 1 file changed, 1 insertion(+) diff --git a/des