A few fixes to prevent compositor crashes
authorAndy Nichols <andy.nichols@nokia.com>
Tue, 5 Jun 2012 13:41:59 +0000 (15:41 +0200)
committerJørgen Lind <jorgen.lind@nokia.com>
Wed, 6 Jun 2012 08:14:10 +0000 (10:14 +0200)
commit077067bc8f68a3146430b941ea0f0daa61781f91
tree46502496fab3f8949f3c73e7e6af8df734d3c532
parent123efe5eb255cf0e2408dff3022cf3e0115a11e7
A few fixes to prevent compositor crashes

If a client application exits abruptly while in direct
rendering mode, the surface buffer could reference a null buffer.
We now check for this before attempting to use such a surface
buffer.  It is also possible for WaylandSurfaceNode::preprocess to
be called after WaylandSurfaceItem has called surfaceDestroyed, so
now we check for a valid surface in preprocess as well.

Change-Id: Ibca71349b7a24687944f8b6cd505941b580e0c2a
Reviewed-by: Paul Olav Tvete <paul.tvete@nokia.com>
Reviewed-by: Jørgen Lind <jorgen.lind@nokia.com>
src/compositor/compositor_api/waylandsurfacenode.cpp
src/compositor/wayland_wrapper/wlsurface.cpp
src/compositor/wayland_wrapper/wlsurfacebuffer.cpp