What I'm looking for is a way to cause this to happen by running a single application and performing a particular action in it. Even if it takes a number of tries that's fine. I just need to be able to trigger somewhat reliably within a few minutes.
I know exactly the part of the codebase that is getting sent into this loop, but I simply don't understand how it's getting there. You can determine which application is the culprit by looking in "~/.cache/upstart/hud.log". In there you'll probably see it mentioning an application hitting a "safety value". The app will have an ID like ":1.22". If you use the application d-feet (see screenshot above) you will be able to figure out which application it is. The IDs are temporary, so if the window has closed, you won't be able to find out what application it was. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1300722 Title: hud-service is eating up 100% of one of my CPUs in a poll loop To manage notifications about this bug go to: https://bugs.launchpad.net/hud/+bug/1300722/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
