gwibber uses a high amount of cpu 98%+ when refreshing

[Dave Morley]

on the whole gwibber and gwibber service isn't showing up on the "top" radar at all untill it comes time to refresh at that point all hell breaks loses and the cpu meter goes off the scale.

ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: gwibber 3.1.2-0ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-5.6-generic 3.0.0-rc7
Uname: Linux 3.0.0-5-generic i686
NonfreeKernelModules: wl
Architecture: i386
Date: Sun Jul 17 23:18:28 2011
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha i386 (20110705.1)
ProcEnviron:
 LANGUAGE=en_GB:en
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SourcePackage: gwibber
UpgradeStatus: No upgrade log present (probably fresh install)

[Victor Vargas (kamus)]

I have noticed the same behaviour with the latest release of gwibber and gwibber-service included in Oneiric, sent to upstream for now.

[Alex Cockell (alcockell)]

Any chance the fix could be SRU'd to Lucid if Lucid is still in life when fixed?

[Omer Akram (om26er)]

Alex, this bug is specific to the version of gwibber in Ubuntu 11.10 Alpha

On Mon, Jul 25, 2011 at 10:38 PM, Alex Cockell
<email address hidden> wrote:
> Any chance the fix could be SRU'd to Lucid if Lucid is still in life
> when fixed?
>
> --
> You received this bug notification because you are subscribed to gwibber
> in Ubuntu.
> https://bugs.launchpad.net/bugs/812043
>
> Title:
>  gwibber uses a high amount of cpu 98%+ when refreshing
>
> Status in Gwibber:
>  New
> Status in “gwibber” package in Ubuntu:
>  Triaged
>
> Bug description:
>  on the whole gwibber and gwibber service isn't showing up on the "top"
>  radar at all untill it comes time to refresh at that point all hell
>  breaks loses and the cpu meter goes off the scale.
>
>  ProblemType: Bug
>  DistroRelease: Ubuntu 11.10
>  Package: gwibber 3.1.2-0ubuntu1
>  ProcVersionSignature: Ubuntu 3.0.0-5.6-generic 3.0.0-rc7
>  Uname: Linux 3.0.0-5-generic i686
>  NonfreeKernelModules: wl
>  Architecture: i386
>  Date: Sun Jul 17 23:18:28 2011
>  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha i386 (20110705.1)
>  ProcEnviron:
>   LANGUAGE=en_GB:en
>   LANG=en_GB.UTF-8
>   SHELL=/bin/bash
>  SourcePackage: gwibber
>  UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/gwibber/+bug/812043/+subscriptions
>

[Bruce Pieterse (octoquad)]

This bug still seems to be present. When refreshing a stream it uses anything from 90 to 100% CPU usage. The app becomes unresponsive and the streams, in my case, never get refreshed. This also applies to user streams.

Running the application in debug mode, I can see that I'm timing out when trying to retrieve messages:
** (gwibber:9030): WARNING **: service.vala:185: Timeout was reached
** (gwibber:9030): DEBUG: streams.vala:226: Getting transient model
** (gwibber:9030): DEBUG: streams.vala:228: transient_model from resources has 0 rows
** (gwibber:9030): DEBUG: streams.vala:291: refresh_transient_model_async

** (gwibber:9030): WARNING **: streams.vala:157: Timeout was reached

(gwibber:9030): Json-CRITICAL **: json_node_get_array: assertion `node != NULL' failed

(gwibber:9030): Json-CRITICAL **: json_array_get_length: assertion `array != NULL' failed

(gwibber:9030): Json-CRITICAL **: json_array_get_length: assertion `array != NULL' failed
** (gwibber:9030): DEBUG: streams.vala:330: Parsed 0 messages in 0.050000ms

** (gwibber:9030): WARNING **: streams.vala:157: Timeout was reached

(gwibber:9030): Json-CRITICAL **: json_node_get_array: assertion `node != NULL' failed

(gwibber:9030): Json-CRITICAL **: json_array_get_length: assertion `array != NULL' failed

(gwibber:9030): Json-CRITICAL **: json_array_get_length: assertion `array != NULL' failed
** (gwibber:9030): DEBUG: streams.vala:330: Parsed 0 messages in 0.039000ms
** (gwibber:9030): DEBUG: streams.vala:302: Fetched and parsed 2 searches in 50192.462000ms

** (gwibber:9030): WARNING **: streams.vala:820: Timeout was reached
** (gwibber:9030): DEBUG: streams.vala:310: Fetched and parsed 0 transient streams in 25023.907000ms
** (gwibber:9030): DEBUG: streams.vala:311: Storing gwibber.transient_model
** (gwibber:9030): DEBUG: streams.vala:313: transient_model has 0 rows

[Bruce Pieterse (octoquad)]

I would also like to add the GUI does not need to be open when gwibber-service utilises 90-100% CPU usage.