touch-packages team mailing list archive

[KrautOS <1199877@xxxxxxxxxxxxxxxxxx>]

This is still an hard issue with up to date trusty, i'm only able to
write this with running:

while true; do sleep 5 && kill -s 1 $(pgrep unity-panel-ser); done

That's keep the system alive under "heavy load" from repeated
Thunderbird messages and probably "indicator-notifications".

dpkg -l | egrep ^ii | egrep -o indicator-\\S*

indicator-appmenu
indicator-bluetooth
indicator-cpufreq
indicator-datetime
indicator-keyboard
indicator-messages
indicator-notifications
indicator-power
indicator-printers
indicator-session
indicator-sound

Nice to watch the "balloning" ;)

top -p $(pgrep unity-panel-ser)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1199877

Title:
  unity-panel-service memory leak and 100% CPU usage

Status in The Application Menu:
  Fix Released
Status in Application Menu Indicator 13.10 series:
  Fix Released
Status in The Ubuntu Power Consumption Project:
  Fix Released
Status in Unity:
  Invalid
Status in Ubuntu:
  Fix Released
Status in “indicator-appmenu” package in Ubuntu:
  Fix Released
Status in “unity” package in Ubuntu:
  Invalid
Status in The Saucy Salamander:
  Fix Released
Status in “indicator-appmenu” source package in Saucy:
  Fix Released

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