Bug 281001 - thunderbird is the process that wakes the cpu up most often on my system
thunderbird is the process that wakes the cpu up most often on my system
Product: Fedora
Classification: Fedora
Component: thunderbird (Show other bugs)
All Linux
medium Severity low
: ---
: ---
Assigned To: Gecko Maintainer
Fedora Extras Quality Assurance
Depends On:
Blocks: wakeup
  Show dependency treegraph
Reported: 2007-09-06 13:33 EDT by Thorsten Leemhuis
Modified: 2009-07-14 12:57 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2009-07-14 12:57:04 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Thorsten Leemhuis 2007-09-06 13:33:58 EDT
Description of problem:
I'm here to do nottings "reducing power usage of Fedora - how you can help!"
effort ( http://article.gmane.org/gmane.linux.redhat.fedora.testers/50480 )

Result on a Santa-Rosa Notebook (x86_64, rawhide)

> [...]
>Top causes for wakeups:
>  21.9% ( 13.1)   thunderbird-bin : futex_wait (hrtimer_wakeup) 
>  14.7% (  8.8)                 X : do_setitimer (it_real_fn) 
>  11.6% (  6.9)    gnome-terminal : schedule_timeout (process_timeout) 
>   7.3% (  4.4)          stardict : schedule_timeout (process_timeout) 
> [...]

From #fedora-devel:

knurd>   | ping notting -- from powertop "18,4% ( 11,1)   thunderbird-bin :
futex_wait (hrtimer_wakeup)"; is that worth filing a bug or is that more a
"stupid user should not have three imap accounts"?

notting> | knurd: it's probably worth filing a bug

Version-Release number of selected component (if applicable):

Additional informations:
I have three imap accounts configured in thunderbird; two for my local network
(dovecot on a F7 server) and on from work (cyrus iirc); all three connect via
ssl; mail-notification connects to those servers as well, but wakes only seldom:
 3.7% (  2.2)   mail-notificati : schedule_timeout (process_timeout)
Comment 1 Bug Zapper 2008-05-13 23:12:01 EDT
Changing version to '9' as part of upcoming Fedora 9 GA.
More information and reason for this action is here:
Comment 2 Bug Zapper 2009-06-09 18:49:22 EDT
This message is a reminder that Fedora 9 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 9.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '9'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 9's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 9 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
Comment 3 Bug Zapper 2009-07-14 12:57:04 EDT
Fedora 9 changed to end-of-life (EOL) status on 2009-07-10. Fedora 9 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

Note You need to log in before you can comment on or make changes to this bug.