** Description changed: + [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://github.com/lxde/menu-cache/issues/) - currently there are 5 reported there, but I'd like to report specifically for the menu-cached process using 100% of CPU (we also have an issue opened on Github for this with lots of comments: https://github.com/lxde/menu- cache/issues/7). 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-cache3:amd64 1.0.1-1build1 amd64 - + ii libmenu-cache-bin 1.0.1-1build1 amd64 + ii libmenu-cache3:amd64 1.0.1-1build1 amd64 Thanks
** Description changed: + For 17.10, please treat this as a 0-day SRU bug report. + [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://github.com/lxde/menu-cache/issues/) - currently there are 5 reported there, but I'd like to report specifically for the menu-cached process using 100% of CPU (we also have an issue opened on Github for this with lots of comments: https://github.com/lxde/menu- cache/issues/7). 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-cache3:amd64 1.0.1-1build1 amd64 Thanks -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1635438 Title: menu-cached process is using 100% CPU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/menu-cache/+bug/1635438/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
