dx-packages team mailing list archive
-
dx-packages team
-
Mailing list archive
-
Message #05356
[Bug 1199877] Re: unity-panel-service memory leak and 100% CPU usage
3.8.6-0ubuntu2 + 13.01.0+13.10.20131031-0ubuntu1, can't reproduce heavy
CPU load (thanks!) but I do still see some heap growth. I ran gimp,
libreoffice, firefox for 296 seconds and observed:
heap change:
88 brk() calls, growth of 11496K, or ~38.75K/sec growth
CPU usage:
4.38% (3.95% user, 0.43 system)
~11 minor page faults/second
So it still seems to be consuming memory quite quickly for me.
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dx-packages, dx-packages
https://bugs.launchpad.net/bugs/1199877
Title:
unity-panel-service memory leak and 100% CPU usage
Status in The Application Menu:
Fix Committed
Status in Application Menu Indicator 13.10 series:
Fix Committed
Status in The Ubuntu Power Consumption Project:
New
Status in Unity:
Invalid
Status in “gtk+3.0” package in Ubuntu:
Fix Released
Status in “indicator-appmenu” package in Ubuntu:
In Progress
Status in “unity” package in Ubuntu:
Invalid
Status in “gtk+3.0” source package in Saucy:
Fix Committed
Status in “indicator-appmenu” source package in Saucy:
Fix Committed
Bug description:
Impact: high CPU/memory usage from unity-panel-service
Test case:
Open a large image in the GIMP and activate a lot of items from the
global menu. Using shortcuts is enough and faster to reproduce this
bug (I've always used Ctrl+A and Ctrl+Shift+A). Memory usage of unity-
panel-service increases steadily and it uses a lot of CPU shortly
after activating the menu items in a short time.
Regression potential: check that the menus are stable/working as they
should
---------
Just going about my business on Ubuntu Raring amd64 on an x230 and I heard the fan kick into action. top showed me that unity-panel-service was consuming all the free cycles on one of my CPUs. I killed it before my machine overheated, so I didn't attach a debugger to see why it was totally pegging out a CPU.
I'm not sure if this adds any context, but I was using a LibreOffice
spreadsheet and I could not insert a table because the menu had lost
it's mind, and then I observed the overly loaded CPU a very short
while after that.
To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-appmenu/+bug/1199877/+subscriptions