Description of problem:
gnome-terminal fully utilizes a CPU when it's doing nothing.
Version-Release number of selected component (if applicable):
Hm. This was a problem yesterday, and a problem earlier this morning. After
logging out and logging back in, I'm no longer seeing it.
I consistently see this too. I have my session set up to bring up two
gnome-terminals when I log in, on different workspaces. Until I switch to the
second workspace, something is using all the CPU. The first gnome-terminal is
displayed and active when I log in. Switching to the second workspace, causing
the second gnome-terminal to be displayed and active, makes the CPU usage drop back.
If you run "xterm" then "gnome-terminal" within that, do you see any messages in
the xterm window?
I updated glibc to 2.3.1-30 and XFree86 to 220.127.116.11-20021230.0, from RedHat
Rawhide, and now the problem is gone.
I am also seeing this on restart (three gnome-terminal sessions running). If I
kill the sessions and restart them everything is OK
Oops, I spoke too soon. I still see this problem even with the updated glibc
and XFree86. As to Warren Togami's question, starting a gnome-terminal from an
xterm does not produce any messages (error or otherwise) in the xterm.
Please try vte-0.10.9; this may fix it for you.
I have upgraded to vte-0.10.10-1 from rawhide. The problem seems to have gone
away--it would almost always (always?) happen the first time I log in after
booting, and I rebooted and logged in without seeing it.
*** Bug 87779 has been marked as a duplicate of this bug. ***
gnome-terminal continues to use lots of CPU in rendering text as it flies by
quickly, but it no longer has the RENDER-less X server huge CPU and memory usage
bug since at least Shrike. I would recommend closing this bug unless you can
still reproduce it.
Confirming that recent versions of vte are a bit better when it comes to being
idle and not affecting CPU utilization.
Perhaps we should change "gnome-terminal fully utilizes CPU" to "vte uses
massive amounts of CPU when using AA fonts"...?
There were two separate gnome-terminal issues during the last beta cycle:
1) Lack of XRENDER caused huge CPU usage, quickly growing memory, swap storm and
eventually OOM. This was fixed before the release of Shrike.
2) When AA text flies by quickly in a gnome-terminal on certain video cards, it
uses massive amounts of CPU making it far slower than xterm or konsole.
The current title "gnome-terminal fully utilizes CPU" is indicative of #1,
because #2 wouldn't use CPU during inactivity.
The problem I originally reported went away some time ago.