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
2012-01-12 13:53:53 +01:00
2017-01-26 14:00:22 +10:00
2009-05-12 16:43:13 -07:00

Copyright (C) 1999-2009 VMware, Inc.
All Rights Reserved

The code here may be used/distributed under the terms of the standard
XFree86 license.

Documentation on the VMware SVGA Device programming model
has been updated and expanded, and it now lives at:

http://vmware-svga.sourceforge.net/

--
Description
No description provided
Readme 1.8 MiB
Languages
C 98.6%
Makefile 0.7%
M4 0.7%