Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 135672 - gnome-terminal is a cpu hog
Summary: gnome-terminal is a cpu hog
Keywords:
Status: CLOSED DUPLICATE of bug 110154
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-terminal
Version: 2
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Ray Strode [halfline]
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2004-10-14 11:01 UTC by Need Real Name
Modified: 2007-11-30 22:10 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2006-02-21 19:06:18 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)

Description Need Real Name 2004-10-14 11:01:21 UTC 
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.3)
Gecko/20040922

Description of problem:
I have gnome-terminal open with several tabs.

I often find that, for programs that produce a lot of output, I have
to switch to another tab because the cpu usage hits 100%.

As a comparison, I ran perl -dDProf script.pl with xboth term and
gnome-germinal.

xterm
real    0m19.997s
user    0m1.304s
sys     0m0.467s

gnome-terminal
real    3m54.364s
user    0m1.301s
sys     0m0.470s

From the results, gnome-terminal seems to use the same amount of cpu
time, but takes more than 10 times longer to run.

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


How reproducible:
Always

Steps to Reproduce:
x

Additional info:
Comment 1 Barry K. Nathan 2004-10-18 05:03:11 UTC 
I think this is a dupe of 110154
Comment 2 Need Real Name 2004-10-18 06:54:19 UTC 

*** This bug has been marked as a duplicate of 110154 ***
Comment 3 Red Hat Bugzilla 2006-02-21 19:06:18 UTC 
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.
Note You need to log in before you can comment on or make changes to this bug.