On Fri, 2009-03-13 at 09:45 +0100, Lukas Ruetz wrote: > On Mon, 09 Mar 2009 12:36:40 +0100, Lukas Ruetz <[email protected]> wrote: > >>> My application is a simple version of an image-slideshow. When the next > >>> image is shown I call clutter_actor_destroy(previousActor) on the old > >>> actor. > >>> Is that enough to free the memory used by the texture? > >> > >> yes. > > Hi, > > please let me ask once again. Also this simple test-app I've attached does > not free the image-memory during runtime. If calling > clutter_actor_destroy() > is enough as you say, then why is the memory not freed?
let me tell you once again: Clutter uses the slice allocator from GLib, which pre-allocates memory regions (called "magazines") and manages the reclamation of the released memory and hand-out of new allocations. the memory usage is stable. please, read: http://library.gnome.org/devel/glib/stable/glib-Memory-Slices.html and: http://library.gnome.org/devel/gtk-faq/stable/x702.html if you use valgrind following the instructions of the wiki page I linked in my first reply you'll see that the memory usage is correct. ciao, Emmanuele. -- Emmanuele Bassi, Intel Open Source Technology Center -- To unsubscribe send a mail to [email protected]
