On Mon, Apr 18, 2011 at 5:47 PM, Joe Vanderstelt <[email protected]> wrote: > I have had the same problem killing gnome-do and restarting is the only fix > I found > > On Apr 18, 2011 6:44 PM, "Sean Dague" <[email protected]> wrote: >> Relatively frequently (like every couple of days), when I resume my >> laptop gnome-do will go to 100%+ CPU and stay there until I kill it. I >> typically only notice it after my fan has pegged on my laptop (or worse, >> after it's been doing it for an hour draining my battery). >> >> Is there any suggestions on what might be causing this, or how to debug >> it? >> >> -Sean
If you do a: kill -SIGQUIT <pid of gnome do> it will dump a stack trace to the *original terminal* Do was started from. If it auto-started, this should dump it into ~/.xsession-errors That trace should give insights into what it is doing, and possibly indicate which plugin (if any) is causing this so you can temporarily disable it. - Rob -- You received this message because you are subscribed to the Google Groups "GNOME Do" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/gnome-do?hl=en.
