Interestingly, the problem is also seen if chromium is restarted and one of the tabs is http://translate.google.com - closing that tab resolves the cpu usage issue, and subsequently opening a new tab and going to http://translate.google.com does *not* manifest the problem.
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1321602 Title: chromium browser chews 100% CPU in epoll_wait() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1321602/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
