It went back to using full CPU a few minutes later. Opening and poking
at gwibber didn't have any effect this time. But it's now gone back to
using no CPU again without further intervention.
I tried attaching strace to it, but just got:
restart_syscall(<... resuming interrupted call ...>
** Also affects: gwibber (Ubuntu)
Importance: Undecided
Status: New
--
gwibber-daemon takes too much cpu
https://bugs.launchpad.net/bugs/451360
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
