Ubuntu
gwibber package

  1. Bug #451360
  2. Comment #4

Comment 4 for bug 451360

Revision history for this message
Martin Ling (martin-launchpad) wrote :

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 ...>