gwibber-service stays at 90% cpu after adding twitter account

Bug #545841 reported by Andrew Fenn on 2010-03-24
130
This bug affects 28 people
Affects Status Importance Assigned to Milestone
Gwibber
Undecided
Unassigned
gwibber (Ubuntu)
Undecided
Unassigned

Bug Description

Binary package hint: gwibber

Steps:
1) Installed a clean version of Ubuntu 10.04 beta and updated all packages.
2) Added my twitter account details and observed that my messages show up as expected

The problem is that after doing this and closing the Gwibber window, the gwibber-service process continues in the background running constantly at 80 to 90% cpu.

pcollaog (pcollaog) wrote :

I have 2 account, one to twitter and other for statusnet (own instalation) and gwibber-service works with cpu 100%

pcollaog (pcollaog) wrote :

This error appear always and cpu growing 100%

Gwibber Dispatcher: DEBUG <statusnet:private> Finished operation
Gwibber Dispatcher: INFO Loading complete: 3 - ['Failure', 'Success', 'Success', 'Success', 'Success', 'Success']
Gwibber Dispatcher: DEBUG ** Starting Refresh - Wed Mar 24 17:23:06 2010 **
Gwibber Dispatcher: DEBUG <twitter:receive> Performing operation
Gwibber Dispatcher: ERROR <twitter:receive> Operation failed
Gwibber Dispatcher: DEBUG Traceback:
Traceback (most recent call last):
  File "/usr/lib/python2.6/dist-packages/gwibber/microblog/dispatcher.py", line 64, in perform_operation
    message_data = PROTOCOLS[account["protocol"]].Client(account)(opname, **args)
  File "/usr/lib/python2.6/dist-packages/gwibber/microblog/twitter.py", line 146, in __call__
    return getattr(self, opname)(**args)
  File "/usr/lib/python2.6/dist-packages/gwibber/microblog/twitter.py", line 149, in receive
    return self._get("statuses/home_timeline.json", count=count, since_id=since)
  File "/usr/lib/python2.6/dist-packages/gwibber/microblog/twitter.py", line 136, in _get
    if data.has_key("error"):
AttributeError: 'list' object has no attribute 'has_key'

Gwibber Dispatcher: DEBUG <twitter:private> Performing operation
Gwibber Dispatcher: DEBUG <twitter:private> Finished operation
Gwibber Dispatcher: DEBUG <statusnet:receive> Performing operation
Gwibber Dispatcher: DEBUG <statusnet:receive> Finished operation
Gwibber Dispatcher: DEBUG <statusnet:responses> Performing operation
Gwibber Dispatcher: DEBUG <statusnet:responses> Finished operation
Gwibber Dispatcher: DEBUG <statusnet:private> Performing operation
Gwibber Dispatcher: DEBUG <statusnet:private> Finished operation
Gwibber Dispatcher: ERROR Loading failed: - Traceback (most recent call last):
  File "/usr/lib/python2.6/dist-packages/gwibber/microblog/dispatcher.py", line 339, in run
    pool.map_async(self.func, self.iterable, callback=self.callback).get(self.timeout)
  File "/usr/lib/python2.6/multiprocessing/pool.py", line 418, in get
    raise TimeoutError
TimeoutError

Mark M. (earlmagnus) wrote :

The same happens with me, though my logs are more innocuous. It appears that on the first refresh after startup, the gwibber service starts to consume 100% of one of my CPUs.

My log has a facebook failure when the CPU consumption starts:

2010-03-31 17:02:40,178 - Gwibber Dispatcher - ERROR - <facebook:images> Operation failed
2010-03-31 17:02:40,181 - Gwibber Dispatcher - INFO - Loading complete: 2 - ['Success', 'Success', 'Failure']

Sean McColgan (mccolgst-gmail) wrote :

Thank you for reporting this bug. Do either of these bugs sound similar to the problem you have here?
Bug #549108
Bug #548540

Thank you

Darren Walsh (darrenbwalsh) wrote :

I have the same problem, and it doesnt seem to be the same as Bug #549108 or Bug #548540

Leo (llenchikk) wrote :

I have tha same issue. I have twitter account, and gwibber-service takes 100% CPU after few minutes of starting system.

Omer Akram (om26er) wrote :

This might be related to bug 530605

Schorsch (schorschi-schorsch) wrote :

Same for me. I currently almost let my netbook get in flames, cause my cpu oveheated. Permanently 100% of cpu-usage by the process gwibber-service.

I use Ubuntu Netbook Edition. Just one Twitter-account in gwibber.

Mark M. (earlmagnus) wrote :

> This might be related to bug 530605

Perhaps, but in my case, Erlang is already running in the background and using the personal couchdb. That never causes CPU issues.

Asif Youssuff (yoasif) wrote :

How can I test whether it is couchdb that is causing the issue? Evolution never seems to give me any issues.

Same happens here. Happened with a Single Facebook Account (which I deleted) and is now happening with 2 twitter accounts.

Also, when I end the service it takes not only 100% of 1CPU, but 100% of all Core i7 CPUs (displayed as 400%) for a few seconds.

s.moog (mail-susanne-moog) wrote :

Same here, as described in comment #11. Are there any additional infos you need?

Omer Akram (om26er) wrote :

Thanks for taking time to report this bug and help make ubuntu better. This particular bug has already been reported but feel free to report any other bug you may find

I am experiencing the same (or a similar) issue. I added both a Facebook and a Twitter account to Gwibber and after login the gwibber-service stays at 100% CPU.

Let me know if you need more information.

Ball Choi (vegetableball) wrote :

I also have this problem.
10.04 beta 1, updated from 9.10
I have only added a facebook account.
Launch gwibber, and close it into tray. Then I have my CPU full-loaded.
gwibber-service contributes most of the loading.

Jeffrey Flaker (jflaker) wrote :

Not sure what the service offers without the application running......For me, it just sucks down CPU....I believe that for most everyone, it the service was stopped on gwibber close, it would be a plus.

For now, everytime I exit gwibber, I must go into system monitor and kill the 2-5 gwibber-service instances to get my computer CPU back.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Bug attachments