> Re: at-spi2-core-debuginfo > You need to enable core-debug repo :) Thank you :) added to my notes
I'm not sure about #13 either. Most of these allocations seem to happen in libdbus, this one might be part of something larger that got lost. I have valgrind.log that is small enough to attach as a whole, from a new C-sample that reproduces the leak. Maybe that helps, we'll see. I've opened an upstream bug report and attached everything there. https://bugzilla.gnome.org/show_bug.cgi?id=730152 ** Bug watch added: GNOME Bug Tracker #730152 https://bugzilla.gnome.org/show_bug.cgi?id=730152 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to at-spi2-core in Ubuntu. https://bugs.launchpad.net/bugs/1317436 Title: onboard memory usage/cpu increase and lockup Status in Onboard on-screen keyboard: Invalid Status in “at-spi2-core” package in Ubuntu: New Bug description: I am running onboard in Mageia 5 (Cauldron) and recently I'm seeing a total lock-up of onboard after the machine has been running for over 24 hours. The tray icon is there but does nothing. At this point onboard is using 25% cpu and 880MB ram.. I am attaching the memory usage analysis for onboard (after the lockup) in the hope that it will be of use. In the meantime I will try to monitor memory usage over a day to see if this increase is gradual or happens suddenly. To manage notifications about this bug go to: https://bugs.launchpad.net/onboard/+bug/1317436/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
