menu-cached process is using 100% CPU
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
menu-cache (Ubuntu) |
Fix Released
|
High
|
Simon Quigley | ||
Xenial |
Fix Released
|
High
|
Simon Quigley | ||
Artful |
Fix Released
|
High
|
Simon Quigley | ||
Bionic |
Fix Released
|
High
|
Simon Quigley |
Bug Description
[Impact]
Without this bugfix, users who resume from suspend will be greeted with a heavy CPU load when they resume. This is especially bad for older computers who may not be able to hand a large CPU load, and menu-cache is included by default in Lubuntu, where this is especially important.
[Test Case]
1. Suspend your computer with the menu-cache process running.
2. Resume from suspend.
3. Try to press Alt + F2 or use any other program which calls menu-cached.
It should work as normal, but it uses up a lot of CPU power.
[Regression Potential]
This bugfix cherry picks an upstream commit that hasn't been tagged yet. As such, there might be additional improvements before it is released.
Also, this modifies how processes are handled; specifically, it terminates any processes which return a socket error. This could eventually bitrot and result in processes returning valid values but it really shows as an error.
While all of those are theoretical, it is definitely a possibility. Other than those two considerations, the regression risk is low.
[Original Description]
Hey all,
I don't know you guys are looking for the issues opened on Github (https:/
I'm using a brand new installation of Lubuntu 16.10 in my laptop.
I noticed the machine temperature was too hot (96 degrees!!!) so I took a look on top and the menu-cached was the guilty. I killed it and everything was as usual again.
I just don't know if it was because I returned from the suspended mode or if it's because I tried to run a custom command with "Open With". I did both in sequence/same session.
$ dpkg -l |grep -iP "menu.*?cache"
ii libmenu-cache-bin 1.0.1-1build1 amd64
ii libmenu-
Thanks
description: | updated |
description: | updated |
Changed in menu-cache (Ubuntu Artful): | |
status: | Fix Committed → Fix Released |
status: | Fix Committed → Fix Released |
status: | Fix Committed → Fix Released |
no longer affects: | menu-cache (Ubuntu Zesty) |
no longer affects: | menu-cache (Ubuntu Trusty) |
description: | updated |
This bug was fixed in the package menu-cache - 1.0.2-1
---------------
menu-cache (1.0.2-1) unstable; urgency=medium
* Merging upstream version 1.0.2 (LP: #1635438).
* Bump Standards-Version to 3.9.8.
-- Andriy Grytsenko <email address hidden> Sun, 06 Nov 2016 19:17:53 +0200