The "??" function in the valgrind trace is g_settings_class_init, which is called once when the class is first instantiated. It creates a bunch of signals (eg, g_signal_new in http://git.gnome.org/browse/glib/tree/gio/gsettings.c#n641), and as far as I can tell, never gets rid of them. In fact, searching the glib documentation, it seems like there's no way to get rid of a signal once it is created, as it is global program state.
I'd recommend changing this to "Invalid" and updating the supressions file.
(Hint: The GLib/GIO supressions file was already imported into experimental-memcheck/compiz.supp - I'd suggest using the suppressions from there).
I don't think this is a leak in compiz.
The "??" function in the valgrind trace is g_settings_ class_init, which is called once when the class is first instantiated. It creates a bunch of signals (eg, g_signal_new in http:// git.gnome. org/browse/ glib/tree/ gio/gsettings. c#n641), and as far as I can tell, never gets rid of them. In fact, searching the glib documentation, it seems like there's no way to get rid of a signal once it is created, as it is global program state.
I'd recommend changing this to "Invalid" and updating the supressions file.
(Hint: The GLib/GIO supressions file was already imported into experimental- memcheck/ compiz. supp - I'd suggest using the suppressions from there).