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 134521 - acme+notification area applet producing high CPU load on startup
acme+notification area applet producing high CPU load on startup
Status: RESOLVED DUPLICATE of bug 122327
Product: acme
Classification: Deprecated
Component: general
unspecified
Other other
: Normal normal
: ---
Assigned To: Bastien Nocera
Bastien Nocera
Depends on:
Blocks:
 
 
Reported: 2004-02-16 13:22 UTC by MatzeB
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description MatzeB 2004-02-16 13:22:58 UTC 
Distribution: gentoo linux 1.4
Package: acme
Severity: minor
Version: GNOME2.4.1 unspecified
Gnome-Distributor: Gentoo Linux
Synopsis: acme+notification area applet producing high CPU load on startup
Bugzilla-Product: acme
Bugzilla-Component: general
Bugzilla-Version: unspecified
Description:
Description of Problem:
When starting up gnome, I often (not always) get the problem that
suddenly my CPU load goes up to 100% for around 20 or 30 seconds while
my panel stops loading. Using top shows that acme and the notification
area applet are using all the CPU time here for no apparent reason.

Steps to reproduce the problem:
1. I just start gnome
2. 
3. 

How often does this happen?
Nearly always. However sometimes it works without any problem.

Additional Information:
I'm using a 2.6Ghz P4 system with gentoo linux and acme 2.4.2
notification area applet 2.4.2.




------- Bug moved to this database by unknown@bugzilla.gnome.org 2004-02-16 08:22 -------

The original reporter (matze@braunis.de) of this bug does not have an account here.
Reassigning to the exporter, unknown@bugzilla.gnome.org.
Reassigning to the default owner of the component, hadess@hadess.net.
Comment 1 Bastien Nocera 2004-02-18 10:26:14 UTC 

*** This bug has been marked as a duplicate of 122327 ***