GNOME Bugzilla – Bug 107234
[TRACKER] gnome-terminal crashes [vte_terminal_fork_command]
Last modified: 2005-12-18 13:59:41 UTC
Package: gnome-terminal Severity: normal Version: 2.2.1 Synopsis: gnome-terminal crashes Bugzilla-Product: gnome-terminal Bugzilla-Component: general BugBuddy-GnomeVersion: 2.0 (2.2.0.1) Description: Description of Problem: gnome-terminal with multiple tabs and ssh sessions to remote sites crashes when the network connectivity lapses and attempt made to exit tabs. Steps to reproduce the problem: 1. unknown 2. 3. Actual Results: terminal crashes Expected Results: tabs quit How often does this happen? first time Additional Information: Debian System Debugging Information: Backtrace was generated from '/usr/bin/gnome-terminal' (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)...(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)... (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)...(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)... (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)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)...[New Thread 16384 (LWP 1094)] (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)...(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)... (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)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... 0x40b5fb89 in wait4 () from /lib/libc.so.6
+ Trace 34370
Thread 1 (Thread 16384 (LWP 1094))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2003-02-27 23:29 ------- The original reporter (fade@deepsky.com) of this bug does not have an account here. Reassigning to the exporter, unknown@bugzilla.gnome.org. Reassigning to the default owner of the component, hp@redhat.com.
Looks sort of like the stack trace in bug 106487, but I don't think it's a duplicate. So I'm setting version->2.2.x, marking priority->high & severity->critical (it's a crasher), adding GNOMEVER2.2 and bugsquad keywords, and marking as new.
*** Bug 109401 has been marked as a duplicate of this bug. ***
*** Bug 108974 has been marked as a duplicate of this bug. ***
Bug 108974 was a backtrace from the time configuration of the gnome-system-tools. The reporter of that bug provided the following information: Opened the time configuration window, No problem there. When I close the window without doing anything else, the time configuration tool crashed. backtrace is attached. Package information: Package: gnome-system-tools Installed-Size: 5504 Maintainer: Jose Carlos Garcia Sogo <jsogo@debian.org> Architecture: i386 Version: 0.24.0-1 Backtrace was generated from '/usr/bin/time-admin' Since the OS is currently 'other' and bug 108974 is from Debian, I'm changing the OS to 'All'.
*** Bug 109425 has been marked as a duplicate of this bug. ***
*** Bug 109584 has been marked as a duplicate of this bug. ***
*** Bug 109521 has been marked as a duplicate of this bug. ***
*** Bug 109531 has been marked as a duplicate of this bug. ***
*** Bug 109540 has been marked as a duplicate of this bug. ***
*** Bug 109552 has been marked as a duplicate of this bug. ***
*** Bug 109554 has been marked as a duplicate of this bug. ***
*** Bug 109580 has been marked as a duplicate of this bug. ***
*** Bug 109607 has been marked as a duplicate of this bug. ***
*** Bug 109686 has been marked as a duplicate of this bug. ***
*** Bug 109624 has been marked as a duplicate of this bug. ***
Possibly useful comment from 109624 *************** It turns out that this is only happening when the user's account is hosted on an NFS server. Local accounts only experience the problem once (eg. like my laptop), but after that, I can't get gnome-terminal to crash. However, the NFS accounts are really consistent. Everytime I open a couple windows, run any command in a window, and then close the window, gnome-terminal crashes. I have verified the local vs. NFS behaviour on my desktop and laptop using 3 different user accounts. I captured the error message that gnome-terminal was displaying when it crashed: ** ERROR **: file vte.c: line 7013 (vte_terminal_process_incoming): assertion failed: (_vte_buffer_length(terminal->pvt->incoming) > 0) aborting...
*** Bug 109707 has been marked as a duplicate of this bug. ***
As discussed on #bugs (i.e. this is what aes suggested I should do), this appears to be getting a lot of dups so I'm going to mark up the priority to Urgent and add the TARGET 2.2.2 keyword. We may also want make a tracker bug for this so the poor reporter doesn't get spammed too much...
*** Bug 109761 has been marked as a duplicate of this bug. ***
*** Bug 109477 has been marked as a duplicate of this bug. ***
*** Bug 109764 has been marked as a duplicate of this bug. ***
*** Bug 109784 has been marked as a duplicate of this bug. ***
Created attachment 15423 [details] [review] fix assert vte.c:7013
I have attached a patch which fixes the problem as I was seeing it. vte_process_incoming was called after a timeout with no data because vte_terminal_io_read was scheduling it on eof. So check for no data and do not schedule.
*** Bug 109830 has been marked as a duplicate of this bug. ***
Bugs get fixed more quickly if they're on the right component. ;-)
*** Bug 109859 has been marked as a duplicate of this bug. ***
*** Bug 109845 has been marked as a duplicate of this bug. ***
*** Bug 109924 has been marked as a duplicate of this bug. ***
*** Bug 109983 has been marked as a duplicate of this bug. ***
*** Bug 109985 has been marked as a duplicate of this bug. ***
Adding PATCH keyword. nalin?
This happens a lot on my laptop which doesn't use NFS.
Actually, it does make sense. It seems to occur when my harddrive is spinning with another process. (if I do a "du /" in one tab and repeatedly open and close another tab, eventually it will crash)
*** Bug 110066 has been marked as a duplicate of this bug. ***
*** Bug 110225 has been marked as a duplicate of this bug. ***
What's the status here? I've been using this patch for a while and it works fine. Can it be applied in CVS?
Updating summary to make it easier for others to find duplicates...
*** Bug 111107 has been marked as a duplicate of this bug. ***
Should be fixed in HEAD and the gnome-2-2 branch.
*** Bug 111709 has been marked as a duplicate of this bug. ***
*** Bug 109794 has been marked as a duplicate of this bug. ***
*** Bug 111850 has been marked as a duplicate of this bug. ***
*** Bug 112105 has been marked as a duplicate of this bug. ***
*** Bug 112940 has been marked as a duplicate of this bug. ***
*** Bug 112767 has been marked as a duplicate of this bug. ***
*** Bug 113006 has been marked as a duplicate of this bug. ***
*** Bug 113659 has been marked as a duplicate of this bug. ***
*** Bug 114612 has been marked as a duplicate of this bug. ***
*** Bug 113762 has been marked as a duplicate of this bug. ***
*** Bug 114444 has been marked as a duplicate of this bug. ***
*** Bug 114538 has been marked as a duplicate of this bug. ***
*** Bug 115197 has been marked as a duplicate of this bug. ***
*** Bug 115517 has been marked as a duplicate of this bug. ***
*** Bug 116699 has been marked as a duplicate of this bug. ***
*** Bug 116755 has been marked as a duplicate of this bug. ***
*** Bug 118771 has been marked as a duplicate of this bug. ***
*** Bug 118534 has been marked as a duplicate of this bug. ***
*** Bug 119082 has been marked as a duplicate of this bug. ***
*** Bug 119992 has been marked as a duplicate of this bug. ***
*** Bug 120075 has been marked as a duplicate of this bug. ***
*** Bug 120465 has been marked as a duplicate of this bug. ***
*** Bug 120376 has been marked as a duplicate of this bug. ***
*** Bug 121416 has been marked as a duplicate of this bug. ***
*** Bug 122877 has been marked as a duplicate of this bug. ***
*** Bug 122985 has been marked as a duplicate of this bug. ***
*** Bug 119930 has been marked as a duplicate of this bug. ***
*** Bug 124193 has been marked as a duplicate of this bug. ***
*** Bug 124523 has been marked as a duplicate of this bug. ***
*** Bug 125400 has been marked as a duplicate of this bug. ***
*** Bug 125963 has been marked as a duplicate of this bug. ***
*** Bug 126847 has been marked as a duplicate of this bug. ***
*** Bug 126851 has been marked as a duplicate of this bug. ***
*** Bug 128960 has been marked as a duplicate of this bug. ***
*** Bug 122409 has been marked as a duplicate of this bug. ***
*** Bug 129495 has been marked as a duplicate of this bug. ***
*** Bug 129746 has been marked as a duplicate of this bug. ***
*** Bug 134978 has been marked as a duplicate of this bug. ***
*** Bug 136348 has been marked as a duplicate of this bug. ***
*** Bug 136411 has been marked as a duplicate of this bug. ***
*** Bug 137549 has been marked as a duplicate of this bug. ***
*** Bug 138691 has been marked as a duplicate of this bug. ***
*** Bug 137062 has been marked as a duplicate of this bug. ***
*** Bug 145854 has been marked as a duplicate of this bug. ***
*** Bug 145826 has been marked as a duplicate of this bug. ***
*** Bug 146231 has been marked as a duplicate of this bug. ***
*** Bug 146465 has been marked as a duplicate of this bug. ***
*** Bug 146939 has been marked as a duplicate of this bug. ***
*** Bug 146940 has been marked as a duplicate of this bug. ***
*** Bug 146848 has been marked as a duplicate of this bug. ***
*** Bug 147298 has been marked as a duplicate of this bug. ***
*** Bug 148560 has been marked as a duplicate of this bug. ***
*** Bug 147211 has been marked as a duplicate of this bug. ***
*** Bug 152785 has been marked as a duplicate of this bug. ***
*** Bug 169118 has been marked as a duplicate of this bug. ***
*** Bug 171532 has been marked as a duplicate of this bug. ***
*** Bug 317976 has been marked as a duplicate of this bug. ***