nanogui: memory usage


Previous by date: 28 Nov 2006 21:55:23 +0000 Re: Fonts in nano-X, nxlib, FLTK, albrecht ellinger
Next by date: 28 Nov 2006 21:55:23 +0000 Re: memory usage, Greg Haerr
Previous in thread: 28 Nov 2006 21:55:23 +0000 Re: memory usage, Greg Haerr
Next in thread: 28 Nov 2006 21:55:23 +0000 Re: memory usage, Greg Haerr

Subject: Re: [nanogui] memory usage
From: Junior ####@####.####
Date: 28 Nov 2006 21:55:23 +0000
Message-Id: <10BF473863A.00000761ejr@inbox.com>

>> When I unmap a window, does it relinguishes any memory?
> 
> No.  Unmapping a window just causes the server to send expose
> events to all windows underneath the unmapped window.  The
> window structure stays around, unchanged following map and
> unmap calls.

I believe I have tracked the source that might be related to your comment above.

I have several instances of GrDrawImageFromFile() and GrDrawImageToFit(). In the case of tha latter,
I have an array of images that is initialized at startup and that function simply pulls the correct image as needed.

It looks like if I select an image from this array and map the window, then later timeout and remap the same image (this may happen several times), that seems to be where the memory usage problem is. Since, this image_id (for GrDrawImageToFit()) is fixed in the array, and simply reloaded, I'm not sure why it would use additional memory.
Do I need to FreeImage first? If so, I'll have to reinit the array which shouldn't be necessary. What about GrDrawImageFromFile()? What happens when the window is unmap?

What am I missing?

Thanks,
--Jr.

Previous by date: 28 Nov 2006 21:55:23 +0000 Re: Fonts in nano-X, nxlib, FLTK, albrecht ellinger
Next by date: 28 Nov 2006 21:55:23 +0000 Re: memory usage, Greg Haerr
Previous in thread: 28 Nov 2006 21:55:23 +0000 Re: memory usage, Greg Haerr
Next in thread: 28 Nov 2006 21:55:23 +0000 Re: memory usage, Greg Haerr


Powered by ezmlm-browse 0.20.