desktop-packages team mailing list archive

[Launchpad Bug Tracker <861903@xxxxxxxxxxxxxxxxxx>]

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: gwibber (Ubuntu)
       Status: New => Confirmed

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gwibber in Ubuntu.
https://bugs.launchpad.net/bugs/861903

Title:
  CPU usage shoots up when opening new tweet box

Status in Gwibber:
  Confirmed
Status in “gwibber” package in Ubuntu:
  Confirmed

Bug description:
  Look at the attached image. What I've done is, I've first opened the
  New Tweet box, closed it after a few seconds, and then opened it again
  after a second or two (its open at the time of taking the screenshot).
  Now look at Gnome-system-monitor in the same screen shot. Its clear
  that during the first duration when the box was opened, CPU usage of a
  core went around 75% up (the orange line), and it also took usage of a
  core half-up (the red line). Closing the box then brings usage back to
  normal.

  The CPU sport happens without the need to type anything into the box.
  Just opening it increases the CPU usage, and it isn't clearly evident
  what Gwibber is trying to do in the background, since nothing in the
  gwibber window changes.

  Steps to reproduce:
  1) Open Gwibber
  2) Open Gnome-system-monitor
  3) Click the new tweet button at the top right in the gwibber window.
  4) See CPU usage rise up.

  Expected result:
  CPU usage shouldn't stay risen when the box is open.

  Actual result:
  Just opening the box up brings the CPU usage up, and it doesn't come down until the box is closed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gwibber/+bug/861903/+subscriptions