#796 menu-cached eating cpu

[paledread]

I'm happily running LXDE and lxpanel on an old Motion Computing M1400 tablet under Debian testing.

Finding that something was grabbing all available cpu I checked lxtask to find it was menu-cached. It has been doing so fo about 12 hours. I can kill menu-cached but am not sure of the effects that will have.

[paledread]

Thanks for this.

I'm an amateur but will try to help out with the gdb traces this
evening.

On Mon, 18 Jan 2016 12:26:30 +0000
"Lonely Stranger" lstranger@users.sf.net wrote:

• labels: --> menu-cache
• Group: -->
• Priority: 5 --> 7
• Comment:

Thank you very much for reporting this. It is completely safe to kill
menu-cached process, it will be restarted on demand. Although I would
be happy to find out the source of that issue but I'm not sure if I'm
asking for not too much. The source of CPU eating often could be
found using gdb attached to a running process, doing full backtrace
(thread apply all bt full), continuing (cont), breaking (^C),
then repeating (just because single stop may not reveal the problem,
it's much better to do backtrace few times). Thank you in any case,
could you help with diagnostics or not.

---

** [bugs:#796] menu-cached eating cpu**

Status: open
Group:
Labels: menu-cache
Created: Mon Jan 18, 2016 12:13 PM UTC by paledread
Last Updated: Mon Jan 18, 2016 12:13 PM UTC
Owner: nobody

I'm happily running LXDE and lxpanel on an old Motion Computing M1400
tablet under Debian testing.

Finding that something was grabbing all available cpu I checked
lxtask to find it was menu-cached. It has been doing so fo about 12
hours. I can kill menu-cached but am not sure of the effects that
will have.

---

Sent from sourceforge.net because you indicated interest in
https://sourceforge.net/p/lxde/bugs/796/

To unsubscribe from further messages, please visit
https://sourceforge.net/auth/subscriptions/

--
Chris Dunn

[paledread]

Sorry but you are going to have to lead me by the hand on this.

1. Can I restart menu-cached when logged in? It seems to run at login
   but having killed it, how to restart it?

2. Can you give a longer description of the gdb commands? I have used
   it before but never like this.

Thanks. Would like to assist.

On Mon, 18 Jan 2016 12:26:30 +0000
"Lonely Stranger" lstranger@users.sf.net wrote:

• labels: --> menu-cache
• Group: -->
• Priority: 5 --> 7
• Comment:

Thank you very much for reporting this. It is completely safe to kill
menu-cached process, it will be restarted on demand. Although I would
be happy to find out the source of that issue but I'm not sure if I'm
asking for not too much. The source of CPU eating often could be
found using gdb attached to a running process, doing full backtrace
(thread apply all bt full), continuing (cont), breaking (^C),
then repeating (just because single stop may not reveal the problem,
it's much better to do backtrace few times). Thank you in any case,
could you help with diagnostics or not.

---

** [bugs:#796] menu-cached eating cpu**

Status: open
Group:
Labels: menu-cache
Created: Mon Jan 18, 2016 12:13 PM UTC by paledread
Last Updated: Mon Jan 18, 2016 12:13 PM UTC
Owner: nobody

I'm happily running LXDE and lxpanel on an old Motion Computing M1400
tablet under Debian testing.

Finding that something was grabbing all available cpu I checked
lxtask to find it was menu-cached. It has been doing so fo about 12
hours. I can kill menu-cached but am not sure of the effects that
will have.

---

Sent from sourceforge.net because you indicated interest in
https://sourceforge.net/p/lxde/bugs/796/

To unsubscribe from further messages, please visit
https://sourceforge.net/auth/subscriptions/

--
Chris Dunn

32, Saint Mary Country Club
Charles Town
Saint Mary
Jamaica

Mobile phone : 1 (876) 354 0639

[Lonely Stranger]

Thank you very much for reporting this. It is completely safe to kill menu-cached process, it will be restarted on demand. Although I would be happy to find out the source of that issue but I'm not sure if I'm asking for not too much. The source of CPU eating often could be found using gdb attached to a running process, doing full backtrace (thread apply all bt full), continuing (cont), breaking (^C), then repeating (just because single stop may not reveal the problem, it's much better to do backtrace few times). Thank you in any case, could you help with diagnostics or not.

[paledread]

Thanks for this. I set out this morning to follow this procedure.

Logged out and logged in again to get menu-cached running.

Surprise. menu-cached is running but not sucking up all of the cpu.

What has changed at my end? I changed desktop manager from lightdm to
lxdm. It seems that maybe the problem exists with lightdm but not lxdm?

I'll keep watching, and if the problem occurs again I'll post.

Thanks for your help.

On Wed, 20 Jan 2016 13:24:41 +0200
"Andrej N. Gritsenko" andrej@rep.kiev.ua wrote:

chris dunn has written on Monday, 18 January, at 18:40:

1. Can I restart menu-cached when logged in? It seems to run at login
   but having killed it, how to restart it?

As I wrote already, you're safe to simply kill the process, it is
started on demand and will be started automatically by libmenu-cache
when it is required.

1. Can you give a longer description of the gdb commands? I have used
   it before but never like this.

Attaching to a running process is very similar to what you do when
start one via gdb, actually it just has one more argument to gdb
command, like that:

gdb /usr/lib/menu-cache/menu-cached 12345

where /usr/lib/menu-cache/menu-cached is path to the running binary
and 12345 is PID of the running process.

When executed command above, gdb attaches to the process and process
is stopped at that moment. You can inspect it (using the backtrace
command mentioned before) and let it run again (using 'continue'
command within gdb). To stop it again you can press Ctrl+C on your
keyboard.

Thanks. Would like to assist.

Thank you very much.

--
Chris Dunn

[Lonely Stranger]

I believe this issue is completely fixed in version 1.0.2 of menu-cache. Thank you very much.