Tiago Vignatti 274dca8f2c dix: don't free stranger pointers inside AllocARGBCursor ...

This seems a good convention to follow: if pointers are allocate outside a
given function, then free there as well when a failure occurs.

AllocARGBCursor and its callers were mixing up the freeing of resources and
causing a particular double free inside TileScreenSaver (srcbits and mskbits).

Signed-off-by: Tiago Vignatti <tiago.vignatti@nokia.com>
Reviewed-by: Ander Conselvan de Oliveira <ander.conselvan-de-oliveira@nokia.com>

2011-04-07 19:57:57 +03:00

13 KiB

Raw Blame History

View Raw