After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 713134 - CPU comsumption while "idle"
CPU comsumption while "idle"
Status: RESOLVED INCOMPLETE
Product: geary
Classification: Other
Component: general
unspecified
Other All
: Low normal
: ---
Assigned To: Geary Maintainers
Geary Maintainers
: 751581 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2013-06-11 09:12 UTC by Geary Maintainers
Modified: 2017-10-26 00:20 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Charles Lindsay 2013-11-21 20:18:59 UTC


---- Reported by geary-maint@gnome.bugs 2013-06-11 02:12:00 -0700 ----

Original Redmine bug id: 7070
Original URL: http://redmine.yorba.org/issues/7070
Searchable id: yorba-bug-7070
Original author: Nil Gradisnik
Original description:

I'm using the latest Geary 0.3.1+trunk on Ubuntu 13.04. I really want to use
Geary but looking at the CPU usage is scary.

This is how it usually looks like after a 10min of being open:

http://screencloud.net/img/screenshots/c01af455cf2415cc64cfaadd1a156b22.png

There is always at least only one CPU core at 100% for some reason.

Can I do something to help debug this problem?



---- Additional Comments From geary-maint@gnome.bugs 2013-09-16 08:58:00 -0700 ----

### History

####

#1

Updated by Jim Nelson 5 months ago

  * **Status** changed from _Open_ to _Need Information_

This could help us get started:

$ geary --debug --log-network > geary.log

Close Geary when the CPU pegs at 100% and send the log to geary@yorba.org.

A couple of additional questions:

  1. How many accounts do you have registered in Geary?
  2. In gear menu -> Accounts -> Edit you can tell Geary how far back in your mail store to download. How far back are you going on your accounts?

Thanks!

####

#2

Updated by Nil Gradisnik 5 months ago

Jim Nelson wrote:

> This could help us get started:

>

> $ geary --debug --log-network > geary.log

>

> Close Geary when the CPU pegs at 100% and send the log to geary@yorba.org.

>

> A couple of additional questions:

>

>   1. How many accounts do you have registered in Geary?

>   2. In gear menu -> Accounts -> Edit you can tell Geary how far back in
your mail store to download. How far back are you going on your accounts?

>

> Thanks!

Thanks, I sent the log output.

I did some more testing and I can't seem to find the pattern that's causing
such high cpu consumption. I left Geary running for a few minutes and it was
all ok, I started clicking on emails and switching to different accounts and
it went up to 100% again and didn't go down until I closed it. Very strange.

I have 3 gmail accounts registered in Geary and all of them have the default
'2 weeks back' set.

####

#3

Updated by Nil Gradisnik 5 months ago

  * **Priority** changed from _High_ to _Low_

Removing my accounts and starting from scratch fixed this issue. So this might
not be relevant any more.

####

#4

Updated by Gunter Königsmann 2 months ago

Did experience very high CPU usage when the network isn't working. Might it be
you have encountered http://redmine.yorba.org/issues/7489 ?



--- Bug imported by chaz@yorba.org 2013-11-21 20:19 UTC  ---

This bug was previously known as _bug_ 7070 at http://redmine.yorba.org/show_bug.cgi?id=7070

Unknown Component 
   Using default product and component set in Parameters 
Unknown version " in product geary. 
   Setting version to "!unspecified".
Unknown milestone "unknown in product geary. 
   Setting to default milestone for this product, "---".
Setting qa contact to the default for this product.
   This bug either had no qa contact or an invalid one.
Resolution set on an open status.
   Dropping resolution 

Comment 1 Clar Charron 2014-04-27 00:12:29 UTC
3 versions later, this bug is still a significant issue. I have a very large CPU usage when using geary even when it's idling.
Comment 2 Jim Nelson 2014-05-01 20:11:58 UTC
Can you send us a log to help us get an idea of what's going on?

$ geary --debug --log-network > geary.log

Please send to geary@yorba.org, as it might contain sensitive information.
Comment 3 Michael Gratton 2016-06-05 11:05:23 UTC
*** Bug 751581 has been marked as a duplicate of this bug. ***
Comment 4 Michael Gratton 2016-06-05 11:08:34 UTC
Hi all, as Jim mentioned in comment #2, can you please generate a log when this is occurring, but send it through to me? Thanks!
Comment 5 Michael Gratton 2016-06-05 11:09:51 UTC
Maybe related to Bug 766547, since it's GMail in both cases.
Comment 6 Michael Gratton 2017-10-26 00:20:59 UTC
Closing this bug report as no further information has been provided. Please feel free to reopen this bug report if you can provide the information that was asked for in a previous comment.
Thanks!