On Wed, Jun 4, 2008 at 1:02 PM, Uygar Gumus <[EMAIL PROTECTED]> wrote: > Using version 0.6.4 there are some leaks in clutter code. > > There are five main parts of leak > > 1- clutter_init > 2- clutter_actor_set_position > 3- clutter_stage_hide_cursor > 4- pango_clutter_render_layout > 5- clutter_actor_get_width > > I attached the valgrind output > Can u please check and tell me what can be wrong? > And what can i do to avoid these leaks?
Most of your reported leaks are false positives due to gobject's use of glib's slice allocator. See http://library.gnome.org/devel/glib/stable/glib-running.html for instructions on how to run and debug glib/gobject based applications. To get correct reports from valgrind you need to set the following: G_SLICE=always-malloc This will cause things to be slightly slower, but also reuses memory in ways that is compatible with valgrinds assumptions. /Øyvind K. -- «The future is already here. It's just not very evenly distributed» -- William Gibson http://pippin.gimp.org/ http://ffii.org/ -- To unsubscribe send a mail to [EMAIL PROTECTED]
