desktop-packages team mailing list archive

[James Hunt <873365@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

The "New Message" box/window causes gwibber to consume a lot of cpu and
causes X.org to consume even more.

To create:

1) Open a terminal and run "top".
2) Click the "New Window" icon in gwibber, but do *not* enter text / press return or click "Send". 
3) Wait for a few seconds.
4) Observe that Xorg is now eating most of your CPU in the top window.
5) Observe that gwibber is now the 2nd biggest consumer of cpu in the top window.
6) Focus the gwibber window and press ESCAPE.
7) Observe that Xorg and gwibber processes are no longer eating cpu in the top window.

ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: gwibber 3.2.0.1-0ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-12.20-generic-pae 3.0.4
Uname: Linux 3.0.0-12-generic-pae i686
NonfreeKernelModules: nvidia
ApportVersion: 1.23-0ubuntu3
Architecture: i386
Date: Thu Oct 13 14:56:53 2011
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
ProcEnviron:
 PATH=(custom, user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SourcePackage: gwibber
UpgradeStatus: Upgraded to oneiric on 2011-09-25 (18 days ago)

** Affects: gwibber (Ubuntu)
     Importance: Undecided
         Status: New


** Tags: apport-bug i386 oneiric running-unity

-- 
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/873365

Title:
  gwibber eats cpu when "new message" window visible

Status in “gwibber” package in Ubuntu:
  New

Bug description:
  The "New Message" box/window causes gwibber to consume a lot of cpu
  and causes X.org to consume even more.

  To create:

  1) Open a terminal and run "top".
  2) Click the "New Window" icon in gwibber, but do *not* enter text / press return or click "Send". 
  3) Wait for a few seconds.
  4) Observe that Xorg is now eating most of your CPU in the top window.
  5) Observe that gwibber is now the 2nd biggest consumer of cpu in the top window.
  6) Focus the gwibber window and press ESCAPE.
  7) Observe that Xorg and gwibber processes are no longer eating cpu in the top window.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: gwibber 3.2.0.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.0.0-12.20-generic-pae 3.0.4
  Uname: Linux 3.0.0-12-generic-pae i686
  NonfreeKernelModules: nvidia
  ApportVersion: 1.23-0ubuntu3
  Architecture: i386
  Date: Thu Oct 13 14:56:53 2011
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
  ProcEnviron:
   PATH=(custom, user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: gwibber
  UpgradeStatus: Upgraded to oneiric on 2011-09-25 (18 days ago)

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