GNOME Bugzilla – Bug 144317
gnome-terminal crashes during two simultaneous tab operations
Last modified: 2004-12-22 21:47:04 UTC
Description of the crash: Opening new tab in exactly the same moment another tab (one of two existing) in the same window is closed, sometimes causes a crash. Steps to reproduce the crash: 1. Open gnome-terminal window with two tabs. 2. sleep 1 ; exit 3. Wait a little, then press Ctrl+Alt+T Expected Results: Two tabs. How often does this happen? Very rare, hard to repeat. Debugging Information: Backtrace was generated from '/opt/gnome/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)...(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)...[Thread debugging using libthread_db enabled] [New Thread 1089622528 (LWP 3585)] (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)...0xffffe410 in ?? ()
+ Trace 47130
Thread 1 (Thread 1089622528 (LWP 3585))
I have spent a while opening and closing tabs and I cannot reproduce this. If you can, could you please recompile gnome-terminal so that we have debugging symbols and get a 'backtrace full' backtrace from gdb?
Not able to repeat. Race condition time seems to be too short. My guess is race condition somewhere in terminal_window_add_screen(), terminal_window_remove_screen(), update_notebook() or gtk_notebook_set_show_*(). Especially strange is, that terminal_window_remove_screen() was running in both threads.
+ Trace 47299
I am not oriented in code, but there can be races in manipulation with window->priv->terms and window->priv->active_term without locking or unref() before actual disappearing from all structures.
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. Note: full backtrace in other bug *** This bug has been marked as a duplicate of 134800 ***