Thomas Hellstrom 79d066da48 saa: Make sure damage destruction happens at the correct location ...

Incorrect DestroyPixmap wrapping previously made the destruction of damage
objects typically happen in damageDestroyPixmap(), leaving a dangling
damage pointer in saa_destroy_pixmap() which was only cleared. However in
some cases that caused us to leak damage objects.

Rework saa initialization somewhat to make sure saa_destroy_pixmap happens
before damageDestroyPixmap and destroy the damage object in saa_destroy_pixmap.
Also add a damage object destruction notifier callback that clears the
saa pixmap damage pointer should the damage object destruction accidentally
happen elsewhere.

This makes sure we don't leak damage objects.

Signed-off-by: Thomas Hellstrom <thellstrom@vmware.com>
Reviewed-by: Deepak Rawat <drawat@vmware.com>

2018-11-29 10:18:39 +01:00

..

Makefile.am

vmware: Fix build warnings

2017-08-07 15:57:56 -07:00

saa_accel.c

saa: Only try to accelerate pixmaps that are driver pixmaps

2011-12-15 08:30:29 +01:00

saa_pixmap.c

saa: Make sure damage destruction happens at the correct location

2018-11-29 10:18:39 +01:00

saa_priv.h

saa: Make sure damage destruction happens at the correct location

2018-11-29 10:18:39 +01:00

saa_render.c

vmwgfx: Use myGlyphs to fix crashes

2013-04-12 11:29:26 +02:00

saa_unaccel.c

vmware/saa: Fix saa_check_poly_fill_rect_noreadback v2

2014-09-24 11:59:06 +02:00

saa.c

saa: Make sure damage destruction happens at the correct location

2018-11-29 10:18:39 +01:00

saa.h

vmware: port vmware driver to new compat API

2012-06-09 05:54:30 +02:00