Hmm, g_type_init only does nothing in trunk glib. Using 2.34 and earlier you need to call it, and it seems to leak by design :(
http://developer.gnome.org/gobject/2.34/gobject-Type-Information.html#g-type-init http://developer.gnome.org/gobject/unstable/gobject-Type-Information.html#g-type-init ** Changed in: compiz Status: Triaged => Incomplete ** Changed in: compiz (Ubuntu) Status: Triaged => Incomplete ** Description changed: I am seeing almost 100 leaks in valgrind all with the same basic stack: ==17459== by 0x7E452E2: g_type_init_with_debug_flags (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.3400.1) ==17459== by 0xAFCF5EC: initBackend (gsettings.c:466) ==17459== by 0xA316D4A: ccsSetBackendDefault (main.c:1268) ==17459== by 0xA3189BB: initGeneralOptions (main.c:266) ==17459== by 0xA318B7C: ccsEmptyContextNew (main.c:334) ==17459== by 0xA31977A: ccsContextNew (main.c:538) + ==17459== by 0xA0DE0FE: CcpScreen::CcpScreen(CompScreen*) (ccp.cpp:509) The docs say not to call g_type_init at all. Maybe that will fix it... ? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1097139 Title: Many leaks (approx 100) in g_type_init_with_debug_flags() from initBackend() from ccsSetBackendDefault() from initGeneralOptions() from ccsEmptyContextNew() from ccsContextNew() To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1097139/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
