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 126519 - Extraordinary CPU/Memory usage
Extraordinary CPU/Memory usage
Status: RESOLVED DUPLICATE of bug 122871
Product: gnome-terminal
Classification: Core
Component: general
2.4.x
Other other
: Normal normal
: ---
Assigned To: GNOME Terminal Maintainers
GNOME Terminal Maintainers
Depends on:
Blocks:
 
 
Reported: 2003-11-08 22:04 UTC by Dave North
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Dave North 2003-11-08 22:05:05 UTC 
Distribution: Unknown
Package: gnome-terminal
Severity: normal
Version: GNOME2.4.0 2.4.x
Gnome-Distributor: FreeBSD GNOME Project
Synopsis: Extraordinary CPU/Memory usage
Bugzilla-Product: gnome-terminal
Bugzilla-Component: general
Bugzilla-Version: 2.4.x
Description:
Description of Problem:
Top shows gnome-terminal using sometimes over 50 percent of cpu and
scads of memory. Scrolling is very slow at times, as is just about
everything on the system.

Steps to reproduce the problem:
1. Start gnome-terminal
2. run 'top'
3. Wiggle the mouse in the terminal window, or do something in another
term window.

Actual Results:
A lot of cpu gets eaten.

Expected Results:
Not so much.

How often does this happen?
Every time so far.

Additional Information:
Sorry, nothing useful. It looks like polling is going nuts, basically.
Don't have a clue why.

Distribution is actually freebsd 4.9; I can't seem to edit the above line, and if I back up I lose the bug report text. Okay, so that should be a bug buddy bug.




------- Bug moved to this database by unknown@bugzilla.gnome.org 2003-11-08 17:05 -------

Reassigning to the default owner of the component, gnome-terminal-maint@bugzilla.gnome.org.
Comment 1 Luis Villa 2004-01-02 18:24:23 UTC 
Marking this a duplicate of bug 122871. That bug has a number of 
questions in it, which, if answered, might help investigate the 
problem. Thanks.

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