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 102713 - launching gnome-terminal w/ multiple tabs hogs cpu at 100% until tabs are visited
launching gnome-terminal w/ multiple tabs hogs cpu at 100% until tabs are vis...
Status: RESOLVED FIXED
Product: gnome-terminal
Classification: Core
Component: general
2.1.x
Other Linux
: Normal major
: ---
Assigned To: Havoc Pennington
GNOME Terminal Maintainers
Depends on:
Blocks:
 
 
Reported: 2003-01-07 01:41 UTC by galeon
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: 2.1/2.2


Description galeon 2003-01-07 01:41:27 UTC 
launching gnome-terminal w/ multiple tabs hogs cpu at 100% until tabs are visited

To repro, launch:
gnome-terminal --disable-factory --tab-with-profile=root --tab-with-profile=root

and witness g-t's CPU usage rise to 100% and stay there until each of the new tabs is visited (I find I need to let the cursor blink once or twice in each tab to get the cpu util to come back down).  Substitute "root" with profile name of choice.

This is with gnome-terminal 2.1.2 and 2.1.3, found in garnome-0.19.3 and .19.5, resp.
Comment 1 Heath Harrelson 2003-01-07 02:57:55 UTC 

*** This bug has been marked as a duplicate of 99220 ***
Comment 2 galeon 2003-01-14 00:42:44 UTC 
Please note that #99220 (which this bug was marked a duplicate of) only discuss opening new tabs within an existing gnome-terminal.  _This_ bug manifests when launching a new instance of gnome-terminal.  It is still a bug in 2.1.4 (with garnome-0.20.0).
Comment 3 galeon 2003-02-09 16:36:57 UTC 
Seems to be fixed with newer vte or something, since garnome-0.21.2 produces a binary that DOES have the problem under the garnome-0.20.0 environment, but that DOES NOT have the problem under 0.21.2.  So sufficiently new libraries seem to solve this problem.

It'd be nice to know which particular library solved the prob, but hey...