Re: [UFO-devel] memory leak3: icons/images

[Johannes S. <sch...@us...>]

On Tuesday 16 August 2005 16:29, Andreas Beckermann wrote:
[...]
> Therefore, when the ufo::UImageIcon object unreference()s all it's
> pointers, the reference count of the image will still be 1 and the image
> won't ever be deleted.
> ufo::UAbstractDisplay::removeVolatileData() is never called, as this would
> be done by the d'tor of ufo::UGL_Image.
>
> In addition: the d'tor of ufo::UAbstractDisplay does not
> 1. delete remaining objects in m_volatileData
> 2. does not emit a warning/error about remaining objects. Very bad for
> debugging.

Oops, that was a rough transition from UContextGroup to UDisplay.
The context group thing is deprecated in favor of a (hopefully) simplified 
design for hardware memory.

The display shall be the main connection to the native system.
It loads system libraries, creates windows and should keep track of allocated 
hardware surfaces/textures.
Everything which is created using the same display shares its data.
So much for the theory.

I'll move the missing parts from UContextGroup to UAbstractDisplay.
This should fix that bug.


Many thanks,
Johannes