I'm working on this today since kenvandine is out. It has been discovered that accessing gnomekeyring from a thread is causing these CPU problems.
What I am going to do is move the calls to gnomekeyring to before gwibber-service starts threads and store that data in mlock()'d memory. Then, replace the previous calls to gnomekeyring to calls to access that mlock()'d memory. I hope to have a branch pushed by end of day for kenvandine to review. -- accessing keyring from python threads sometimes causes 100% CPU utilization https://bugs.launchpad.net/bugs/554005 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
