On Tue, 2008-06-10 at 11:07 +0100, dilip devaraj wrote: > Hello Clutter Team > > I am using the clutter-0.6.2 in my system. I have slightly modified > the test-depth program since the environment does not accept mouse or > keyboard inputs.Hence to end the program I use a timer my making use > of g_timeout_add function and then in callback function i use > clutter_main_quit. > > 1)Using valgrind I am able to see memory leaks wherein memory > allocated during clutter_context_get_default is not freed.Is this a > known issue or am I missing something?
there is only a ClutterMainContext per Clutter process, and its memory is reclaimed automatically by the operating system at the end of the process lifetime, so it's not (by definition) a leak. > 2)Also is any memory check done before a clutter version is > released .If so this would help narrow down the memory leak to the > application. we do profiling with valgrind, yes. [snip on the valgrind log] as I said in the other reply to you about valgrind: you should generate a valgrind suppression file using a minimal clutter program; then you will be able to differentiate the leaked references coming from your application from the ones coming from Clutter. ciao, Emmanuele. -- Emmanuele Bassi, OpenedHand Ltd. Unit R, Homesdale Business Centre 216-218 Homesdale Rd., Bromley - BR12QZ http://www.o-hand.com -- To unsubscribe send a mail to [EMAIL PROTECTED]
