For the indicator-multiload leak, there is a nice valgrind log at https://launchpadlibrarian.net/72194098/valgrind.log (from bug #786425): ==2761== 2,305,980 (45,084 direct, 2,260,896 indirect) bytes in 867 blocks are definitely lost in loss record 11,053 of 11,054 ==2761== ... ==2761== by 0x939692C: gdk_pixbuf_new ==2761== ... ==2761== by 0x7DBE846: IndicatorObjectEntryProxyRemote::GetPixbuf() ==2761== by 0x7DEF2F1: PanelIndicatorObjectEntryView::Refresh() ==2761== ... ==2761== by 0x7DBEF60: IndicatorObjectEntryProxyRemote::Refresh(...) ==2761== by 0x7DC24B6: IndicatorObjectProxyRemote::AddEntry(...) ==2761== by 0x7DC1156: IndicatorObjectFactoryRemote::Sync(...) ==2761== ...
-- You received this bug notification because you are a member of compiz packagers, which is subscribed to compiz in Ubuntu. https://bugs.launchpad.net/bugs/758248 Title: memory leaking in compiz _______________________________________________ Mailing list: https://launchpad.net/~compiz Post to : [email protected] Unsubscribe : https://launchpad.net/~compiz More help : https://help.launchpad.net/ListHelp
