Bug 106487 – Crash while switching tabs

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 106487 - Crash while switching tabs


Summary:	Crash while switching tabs


Status:	VERIFIED INCOMPLETE

Product:	vte
Classification:	Core
Component:	general
Version:	0.10.x
Hardware:	Other other

Importance:	High critical
Target Milestone:	---
Assigned To:	VTE Maintainers
QA Contact:	VTE Maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2003-02-19 01:58 UTC by Francis Reyes
Modified:	2009-08-15 18:40 UTC

See Also:
GNOME target:	---
GNOME version:	2.1/2.2

Description Francis Reyes 2003-02-19 01:53:12 UTC

Package: gnome-terminal
Severity: normal
Version: 2.2.1
Synopsis: Crash while switching tabs
Bugzilla-Product: gnome-terminal
Bugzilla-Component: general
BugBuddy-GnomeVersion: 2.0 (2.2.0.1)

Description:
Description of Problem:
2.2.0 is slow slow slow. Had 4 tabs open with ANSI BitchX running in one
of them and nothing but term's in the rest. Sporadically gnome-terminal
will freeze when switching tabs, taking 99% of cpu. 

Steps to reproduce the problem:
1. 
2. 
3. 

Actual Results:


Expected Results:


How often does this happen?


Additional Information:




Debugging Information:

Backtrace was generated from '/usr/bin/gnome-terminal'

(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...[New Thread 16384 (LWP 2433)]
0x40b37a39 in wait4 () from /lib/libc.so.6

+ Trace 33993

Thread 1 (Thread 16384 (LWP 2433))

#0 wait4
from /lib/libc.so.6
#1 sys_sigabbrev
from /lib/libc.so.6
#2 waitpid
from /lib/libpthread.so.0
#3 libgnomeui_module_info_get
from /usr/lib/libgnomeui-2.so.0
#4 __pthread_sighandler
from /lib/libpthread.so.0
#5 sigaction
from /lib/libc.so.6
#6 _vte_trie_print
from /usr/lib/libvte.so.4
#7 _vte_ring_remove
from /usr/lib/libvte.so.4
#8 vte_terminal_match_check
from /usr/lib/libvte.so.4
#9 vte_terminal_get_encoding
from /usr/lib/libvte.so.4
#10 vte_terminal_set_default_colors
from /usr/lib/libvte.so.4
#11 vte_terminal_fork_command
from /usr/lib/libvte.so.4
#12 g_main_context_wakeup
from /usr/lib/libglib-2.0.so.0
#13 g_get_current_time
from /usr/lib/libglib-2.0.so.0
#14 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#15 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#16 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#17 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#18 main
#19 __libc_start_main
from /lib/libc.so.6
#0 wait4
from /lib/libc.so.6





------- Bug moved to this database by unknown@bugzilla.gnome.org 2003-02-18 20:53 -------

Reassigning to the default owner of the component, hp@redhat.com.

Comment 1 Elijah Newren 2003-02-19 16:50:59 UTC

Appears to be a unique stack trace, according to the
simple-dup-finder.  Setting version->2.2.x, marking priority->high &
severity->critical (it's a crasher), adding GNOMEVER2.2 and bugsquad
keywords, and marking as new.

Comment 2 Nalin Dahyabhai 2003-04-22 06:02:47 UTC

The _vte_trie_print function could only be called in debug mode. 
Please build with --without-debugging if you're concerned about speed.

The stack trace looks dubious: vte_terminal_fork_command() never calls
vte_terminal_set_default_colors().

Please include information about which OS/version you're using, in
case it's a platform-specific issue.

Comment 3 Elijah Newren 2003-06-22 17:42:48 UTC

No response to Nalin's questions--closing.