Page 1 of 1

Destroying GapiRgabSurface doesn't free the memory

PostPosted: Feb 14, 2010 @ 1:38pm
by ageye
when using GapiRgbaSurface with GapiDraw 4.2 it doesn't free the used memory after destroying it (especially when using larger graphics (e.g. > 400x400))
Using C# and
public static extern GapiResult GapiRGBASurface_Destroy(IntPtr pSurface);

Is this a known bug? What can I do to get back the memory?


PostPosted: Feb 17, 2010 @ 3:28pm
by Johan

We have used RGBA surfaces extensively in production software like numerous Sony Ericsson Xperia panels and have not experienced any memory leaks in CGapiRGBASurface (or any other parts of GapiDraw 4.2 for that matte). And we have run many memory allocation tests on the code.

What function are you using the check for available RAM? Maybe it's got something to do with the .NET / DLL integration?