Bug 333739 – gnome-terminal crashes in low-memory conditions

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 333739 - gnome-terminal crashes in low-memory conditions


Summary:	gnome-terminal crashes in low-memory conditions


Status:	RESOLVED OBSOLETE

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

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

URL:
Whiteboard:

Duplicates:	333741 333930 (view as bug list)
Depends on:
Blocks:

Reported:	2006-03-07 13:24 UTC by Pawel Salek
Modified:	2021-06-10 13:24 UTC

See Also:
GNOME target:	---
GNOME version:	2.13/2.14

Description Pawel Salek 2006-03-07 13:24:57 UTC

Distribution: Fedora Core release 4.90 (Pre-FC5)
Package: gnome-terminal
Severity: Normal
Version: GNOME2.13.92 2.13.93
Gnome-Distributor: Red Hat, Inc
Synopsis: gnome-terminal crashes in low-memory conditions
Bugzilla-Product: gnome-terminal
Bugzilla-Component: general
Bugzilla-Version: 2.13.93
BugBuddy-GnomeVersion: 2.0 (2.13.90)
Description:
Description of the crash:
There was a large program running that made the computer swap. I tried
opening another gnome-terminal tab to kill it but gnome-terminal crashed
instead.


Debugging Information:

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

(no debugging symbols found)
Using host libthread_db library "/lib64/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 47482018993664 (LWP 14202)]
[New Thread 1084229968 (LWP 14220)]
(no debugging symbols found)
0x000000340f10cb7f in waitpid () from /lib64/libpthread.so.0

+ Trace 66752

Thread 1 (Thread 47482018993664 (LWP 14202))

#0 waitpid
from /lib64/libpthread.so.0
#1 gnome_init_with_popt_table
from /usr/lib64/libgnomeui-2.so.0
#2 <signal handler called>
#3 FcFontSetSort
from /usr/lib64/libfontconfig.so.1
#4 FcFontSort
from /usr/lib64/libfontconfig.so.1
#5 _vte_fc_patterns_from_pango_font_desc
from /usr/lib64/libvte.so.4
#6 _vte_tree_new
from /usr/lib64/libvte.so.4
#7 vte_terminal_set_font_full
from /usr/lib64/libvte.so.4
#8 _vte_terminal_update_insert_delta
from /usr/lib64/libvte.so.4
#9 g_type_create_instance
from /usr/lib64/libgobject-2.0.so.0
#10 g_object_set
from /usr/lib64/libgobject-2.0.so.0
#11 g_object_newv
from /usr/lib64/libgobject-2.0.so.0
#12 g_object_new_valist
from /usr/lib64/libgobject-2.0.so.0
#13 g_object_new
from /usr/lib64/libgobject-2.0.so.0
#14 vte_terminal_new
from /usr/lib64/libvte.so.4
#15 ??
#16 ??
#17 g_type_create_instance
from /usr/lib64/libgobject-2.0.so.0
#18 g_object_set
from /usr/lib64/libgobject-2.0.so.0
#19 g_object_newv
from /usr/lib64/libgobject-2.0.so.0
#20 g_object_new_valist
from /usr/lib64/libgobject-2.0.so.0
#21 g_object_new
from /usr/lib64/libgobject-2.0.so.0
#22 ??
#23 ??
#24 g_closure_invoke
from /usr/lib64/libgobject-2.0.so.0
#25 g_signal_override_class_closure
from /usr/lib64/libgobject-2.0.so.0
#26 g_signal_emit_valist
from /usr/lib64/libgobject-2.0.so.0
#27 g_signal_emit
from /usr/lib64/libgobject-2.0.so.0
#28 gtk_widget_can_activate_accel
from /usr/lib64/libgtk-x11-2.0.so.0
#29 g_closure_invoke
from /usr/lib64/libgobject-2.0.so.0
#30 g_signal_override_class_closure
from /usr/lib64/libgobject-2.0.so.0
#31 g_signal_emit_valist
from /usr/lib64/libgobject-2.0.so.0
#32 g_signal_emit
from /usr/lib64/libgobject-2.0.so.0
#33 gtk_accel_group_activate
from /usr/lib64/libgtk-x11-2.0.so.0
#34 gtk_accel_groups_activate
from /usr/lib64/libgtk-x11-2.0.so.0
#35 gtk_window_activate_key
from /usr/lib64/libgtk-x11-2.0.so.0
#36 gtk_marshal_BOOLEAN__VOID
from /usr/lib64/libgtk-x11-2.0.so.0
#37 g_closure_invoke
from /usr/lib64/libgobject-2.0.so.0
#38 g_signal_override_class_closure
from /usr/lib64/libgobject-2.0.so.0
#39 g_signal_emit_valist
from /usr/lib64/libgobject-2.0.so.0
#40 g_signal_emit
from /usr/lib64/libgobject-2.0.so.0
#41 gtk_widget_get_default_style
from /usr/lib64/libgtk-x11-2.0.so.0
#42 gtk_propagate_event
from /usr/lib64/libgtk-x11-2.0.so.0
#43 gtk_main_do_event
from /usr/lib64/libgtk-x11-2.0.so.0
#44 gdk_add_client_message_filter
from /usr/lib64/libgdk-x11-2.0.so.0
#45 g_main_context_dispatch
from /usr/lib64/libglib-2.0.so.0
#46 g_main_context_check
from /usr/lib64/libglib-2.0.so.0
#47 g_main_loop_run
from /usr/lib64/libglib-2.0.so.0
#48 gtk_main
from /usr/lib64/libgtk-x11-2.0.so.0
#49 ??
#50 __libc_start_main
from /lib64/libc.so.6
#51 ??
#52 ??
#53 ??





------- Bug created by bug-buddy at 2006-03-07 13:24 -------


Unknown version 2.13.93 in product gnome-terminal.  Setting version to "2.13.x".

Comment 1 Behdad Esfahbod 2006-03-07 22:08:52 UTC

*** Bug 333741 has been marked as a duplicate of this bug. ***

Comment 2 Guilherme de Siqueira Pastore 2006-03-08 17:32:29 UTC

*** Bug 333930 has been marked as a duplicate of this bug. ***

Comment 3 Guilherme de Siqueira Pastore 2006-03-08 17:33:53 UTC

This happens inside vte. Reassigning.

Comment 4 Chris Wilson 2007-02-06 13:08:08 UTC

I'd like to close this report as being NOTGNOME due to the failure inside fontconfig.

However, the reporter has a valid point that g-t could be used by root in extreme conditions and that could be construed as an argument to handle OOM gracefully. Except that our library stack (based on glib) generally throws an error if malloc and friends ever returns NULL. And the entire desktop has to be resilent as well...

The sensible approach seems to be to continual improve our memory usage cf bug 342338.

Comment 5 GNOME Infrastructure Team 2021-06-10 13:24:22 UTC

-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/vte/-/issues/1139.