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 575487 - gnome-terminal hangs when exiting (double free)
gnome-terminal hangs when exiting (double free)
Status: RESOLVED DUPLICATE of bug 572549
Product: gnome-terminal
Classification: Core
Component: general
2.26.x
Other Linux
: Normal critical
: ---
Assigned To: GNOME Terminal Maintainers
GNOME Terminal Maintainers
Depends on:
Blocks:
 
 
Reported: 2009-03-16 05:32 UTC by Priit Laes (IRC: plaes)
Modified: 2009-03-16 12:26 UTC
See Also:
GNOME target: ---
GNOME version: 2.25/2.26


Attachments
gnome-terminal.log (62.90 KB, text/plain)
2009-03-16 10:31 UTC, Priit Laes (IRC: plaes)
Details

Description Priit Laes (IRC: plaes) 2009-03-16 05:32:27 UTC


  • #0 __lll_lock_wait_private
    at ../nptl/sysdeps/unix/sysv/linux/x86_64/lowlevellock.S line 91
  • #1 _L_lock_53
    from /lib/libc.so.6
  • #2 ptmalloc_lock_all
    at arena.c line 261
  • #3 __libc_fork
    at ../nptl/sysdeps/unix/sysv/linux/x86_64/../fork.c line 95
  • #4 fork_exec_with_pipes
    at gspawn.c line 1190
  • #5 IA__g_spawn_sync
    at gspawn.c line 267
  • #6 IA__g_spawn_command_line_sync
    at gspawn.c line 694
  • #7 bugbuddy_segv_handle
    at gnome-breakpad.cc line 369
  • #8 <signal handler called>
  • #9 raise
    at ../nptl/sysdeps/unix/sysv/linux/raise.c line 64
  • #10 abort
    at abort.c line 88
  • #11 __libc_message
    at ../sysdeps/unix/sysv/linux/libc_fatal.c line 170
  • #12 malloc_printerr
    at malloc.c line 5994
  • #13 malloc_consolidate
    at malloc.c line 4897
  • #14 _int_free
    at malloc.c line 4782
  • #15 __libc_free
    at malloc.c line 3625
  • #16 _vte_buffer_free
    at buffer.c line 183
  • #17 _vte_conv_close
    at vteconv.c line 215
  • #18 _vte_iso2022_state_free
    at iso2022.c line 806
  • #19 vte_terminal_finalize
    at vte.c line 8478
  • #20 IA__g_object_unref
    at gobject.c line 2421
  • #21 IA__g_closure_invoke
    at gclosure.c line 767
  • #22 signal_emit_unlocked_R
    at gsignal.c line 3244
  • #23 IA__g_signal_emit_valist
    at gsignal.c line 2977
  • #24 IA__g_signal_emit_by_name
    at gsignal.c line 3071
  • #25 vte_reaper_child_watch_cb
    at reaper.c line 34
  • #26 g_child_watch_dispatch
    at gmain.c line 3631
  • #27 IA__g_main_context_dispatch
    at gmain.c line 1814
  • #28 g_main_context_iterate
    at gmain.c line 2448
  • #29 IA__g_main_loop_run
    at gmain.c line 2656
  • #30 IA__gtk_main
    at gtkmain.c line 1205
  • #31 main
    at terminal.c line 486

Comment 1 Christian Persch 2009-03-16 10:27:34 UTC
Which vte version is that with, 0.20.0 ?

Can you see if you get a different bt when running with MALLOC_CHECK_=2 ? Also a valgrind log might reveal more.
Comment 2 Priit Laes (IRC: plaes) 2009-03-16 10:30:23 UTC
This is with vte-0.19.4

I'll attach the valgrind log.
Comment 3 Priit Laes (IRC: plaes) 2009-03-16 10:31:16 UTC
Created attachment 130732 [details]
gnome-terminal.log
Comment 4 Christian Persch 2009-03-16 10:50:52 UTC
Are you totally absolutely sure this is g-t 2.26.0? This looks like bug 572549 which should be fixed in 2.26.0. And the line numbers don't match up either, e.g.

==23035==    by 0x4232FF: terminal_screen_new (terminal-screen.c:684)
==23035==    by 0x4182BA: terminal_app_new_terminal (terminal-app.c:1792)

but terminal-app.c:1792 doesn't call terminal_screen_new at all.
Comment 5 Priit Laes (IRC: plaes) 2009-03-16 12:26:53 UTC
Marking as dupe..

*** This bug has been marked as a duplicate of 572549 ***