GNOME Bugzilla – Bug 151680
gnome terminal crash
Last modified: 2008-05-29 19:53:49 UTC
Distribution: Fedora Core release 2 (Tettnang) Package: gnome-terminal Severity: normal Version: GNOME2.6. 2.6.x Gnome-Distributor: Red Hat, Inc Synopsis: gnome terminal crash Bugzilla-Product: gnome-terminal Bugzilla-Component: general Bugzilla-Version: 2.6.x BugBuddy-GnomeVersion: 2.0 (2.6.0) Description: When running a bunch of gnome-terminals (60), they crashed. I noticed earlier that the CPU usage was pretty high (40% or so on a P4-2600 CPU). 2.6.0-2 from Fedora Core 2 Debugging Information: Backtrace was generated from '/usr/bin/gnome-terminal' (no debugging symbols found)...Using host libthread_db library "/lib/tls/libthread_db.so.1". (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...[Thread debugging using libthread_db enabled] [New Thread -150431040 (LWP 3855)] (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...0x00392402 in ?? ()
+ Trace 49833
Thread 1 (Thread -150431040 (LWP 3855))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2004-09-02 10:23 ------- Unknown platform unknown. Setting to default platform "Other". Unknown milestone "unknown" in product "gnome-terminal". Setting to default milestone for this product, '---' The original reporter of this bug does not have an account here. Reassigning to the person who moved it here, unknown@bugzilla.gnome.org. Previous reporter was bill-bugbuddy@uncultured.org. Setting to default status "UNCONFIRMED". Setting qa contact to the default for this product. This bug either had no qa contact or an invalid one.
In both cases (152072 is a duplicate), I was running 14 screen sessions on remote computers. I don't know if this matters. ssh otherbox screen The other box (on which screen was running) is running Solaris 9.
*** Bug 152072 has been marked as a duplicate of this bug. ***
Please install some debuginfo packages. This will make the (next) stacktrace much more usefull for the maintainer. See http://fedora.linux.duke.edu/wiki/StackTraces and http://bugzilla.gnome.org/getting-traces.cgi for how to install those. Please install at least: glib2-debuginfo pango-debuginfo gtk2-debuginfo gnome-terminal-debuginfo (not sure about the name) libvte-debuginfo (not sure about the name)
Bug 152278 is a duplicate of this, and was generated with the relevant debuginfo packages installed. Also, I believe that in 2 of the 3 crashes, I was switching between workspaces, both of which had gnome-terminals in them. In the 3rd case, I was switching windows, I believe from gnome-terminal to something else.
Had another crash. Again, it appears to happen when switching windows. Bug-buddy output is below. -------------------------------------- Subject: gnome-terminal crash Distribution: Fedora Core release 2 (Tettnang) Package: gnome-terminal Severity: major Version: GNOME2.6. 2.6.x Gnome-Distributor: Red Hat, Inc Synopsis: gnome-terminal crash Bugzilla-Product: gnome-terminal Bugzilla-Component: general Bugzilla-Version: 2.6.x BugBuddy-GnomeVersion: 2.0 (2.6.0) Description: This is a duplicate of 151680. Again, it appears to happen when switching windows. Debugging Information: Backtrace was generated from '/usr/bin/gnome-terminal' Using host libthread_db library "/lib/tls/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -151164896 (LWP 8981)] 0x002bf7a2 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2
+ Trace 50173
Thread 1 (Thread -151164896 (LWP 8981))
I'm wondering if this is related to bug #126443 ("CPU-bound looping seen in gnome-terminal"). To quote from that bug report: "It seems to be particularly susceptible to the bug when I use the "screen" program over ssh", which is what I'm seeing, too. I am also seeing elevated CPU usage by gnome-terminal, often around 40%.
I ran a few tests. The CPU usage doesn't appear gnome-terminal dependent. It's just a matter of how much data is being dumped to the terminal, and seems the same as xterm. screen doesn't seem to make much difference. ssh does make some difference. A local "ls -R /" seems to generate half the CPU usage by the terminal than a remote (ssh) "ls -R /" does.
Yet another backtrace: Using host libthread_db library "/lib/tls/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -151164896 (LWP 28784)] 0x002d37a2 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2
+ Trace 50293
Thread 1 (Thread -151164896 (LWP 28784))
*** Bug 152278 has been marked as a duplicate of this bug. ***
Unique stacktrace, marking new.
Similar backtrace in bug 163014
This is with a very old version, is probably a gtk bug, probably fixed. Closing.