Bug 354347 – Crash in gedit_plugins_engine_garbage_collect

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 354347 - Crash in gedit_plugins_engine_garbage_collect


Summary:	Crash in gedit_plugins_engine_garbage_collect


Status:	RESOLVED FIXED

Product:	gedit
Classification:	Applications
Component:	general
Version:	2.15.x
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	Gedit maintainers
QA Contact:	Gedit maintainers

URL:
Whiteboard:

Duplicates:	354683 361843 367170 370859 375949 377814 379211 381964 383483 389173 389714 390453 399770 419704 419838 420388 427689 428572 431767 459741 470244 (view as bug list)
Depends on:
Blocks:

Reported:	2006-09-04 21:24 UTC by matteo
Modified:	2007-09-21 16:22 UTC

See Also:
GNOME target:	---
GNOME version:	2.15/2.16

Description matteo 2006-09-04 21:24:34 UTC

Version: 2.15.9

What were you doing when the application crashed?



Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.15.92 2006-08-22 (Ubuntu)
BugBuddy Version: 2.15.92

Memory status: size: 45424640 vsize: 0 resident: 45424640 share: 0 rss: 21897216 rss_rlim: 0
CPU usage: start_time: 1157405047 rtime: 0 utime: 87 stime: 0 cutime:80 cstime: 0 timeout: 7 it_real_value: 0 frequency: 0

Backtrace was generated from '/usr/bin/gedit'

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1210587472 (LWP 4754)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 71593

Thread 1 (Thread -1210587472 (LWP 4754))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/tls/i686/cmov/libpthread.so.0
#2 gnome_gtk_module_info_get
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 PyType_IsSubtype
from /usr/lib/libpython2.4.so.1.0
#5 PyDict_Next
from /usr/lib/libpython2.4.so.1.0
#6 PyDict_Next
from /usr/lib/libpython2.4.so.1.0
#7 initgc
from /usr/lib/libpython2.4.so.1.0
#8 PyGC_Collect
from /usr/lib/libpython2.4.so.1.0
#9 gedit_python_garbage_collect
#10 gedit_plugins_engine_garbage_collect
#11 _gedit_window_move_tab_to_new_window
#12 g_object_run_dispose
from /usr/lib/libgobject-2.0.so.0
#13 gtk_object_destroy
from /usr/lib/libgtk-x11-2.0.so.0
#14 gtk_widget_destroy
from /usr/lib/libgtk-x11-2.0.so.0
#15 gedit_app_get_default
#16 _gedit_app_restore_window
#17 _gtk_marshal_BOOLEAN__BOXED
from /usr/lib/libgtk-x11-2.0.so.0
#18 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#19 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#20 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#21 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#22 gtk_widget_get_default_style
from /usr/lib/libgtk-x11-2.0.so.0
#23 gtk_main_do_event
from /usr/lib/libgtk-x11-2.0.so.0
#24 _gdk_events_init
from /usr/lib/libgdk-x11-2.0.so.0
#25 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#26 g_main_context_check
from /usr/lib/libglib-2.0.so.0
#27 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#28 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#29 main
#0 __kernel_vsyscall

Comment 1 Paolo Maggi 2006-09-04 22:01:39 UTC

Thanks for taking the time to report this bug.
This bug report isn't very useful because it doesn't describe the bug well. If you have time and can still reproduce the bug, please read http://bugzilla.gnome.org/bug-HOWTO.html and add a description of how to reproduce this bug.

Unfortunately, that stack trace is not very useful in determining the cause of the crash. Can you get us one with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so.

Comment 2 Paolo Maggi 2006-09-07 08:58:36 UTC

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

Comment 3 Karsten Bräckelmann 2006-10-13 01:51:11 UTC

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

Comment 4 Paolo Maggi 2006-10-29 16:01:43 UTC

Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for.
Thanks!

Comment 5 André Klapper 2006-10-30 00:08:13 UTC

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

Comment 6 Paolo Maggi 2006-11-05 09:45:55 UTC

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

Comment 7 Paolo Maggi 2006-11-05 09:49:00 UTC

Re-opening since we have duplicates.

Unfortunately, we still lack a good stack trace for this crash.

The reported stack traces are all missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. 

If you are still able to reproduce this crash, can you please get us a stack trace with debugging symbols? 

Please see http://live.gnome.org/GettingTraces for more information on how to do so.

Thanks in advance!

Comment 8 Paolo Maggi 2006-11-05 09:51:27 UTC

[Adding the reporters of the other duplicates too CC list.]

Unfortunately, we still lack a good stack trace for this crash.

The reported stack traces are all missing some elements that will help a lot to
solve the problem, so it will be hard for the developers to fix that crash. 

If you are still able to reproduce this crash, can you please get us a stack
trace with debugging symbols? 

Please see http://live.gnome.org/GettingTraces for more information on how to
do so.

Thanks in advance!

Comment 9 André Klapper 2006-11-17 15:12:07 UTC

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

Comment 10 André Klapper 2006-11-22 00:01:20 UTC

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

Comment 11 Steve Frécinaux 2006-11-26 00:29:09 UTC

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

Comment 12 Damien Durand 2006-12-03 20:50:47 UTC

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

Comment 13 Bruno Boaventura 2006-12-07 21:08:23 UTC

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

Comment 14 Pedro de Medeiros 2006-12-26 14:23:02 UTC

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

Comment 15 Pedro de Medeiros 2006-12-26 16:12:14 UTC

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

Comment 16 Paolo Borelli 2006-12-29 10:40:10 UTC

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

Comment 17 Paolo Maggi 2007-01-21 18:23:50 UTC

Unfortunately, we still lack a good stack trace for this crash.

The reported stack traces are all missing some elements that will help a lot to
solve the problem, so it will be hard for the developers to fix that crash. 

If you are still able to reproduce this crash, can you please get us a stack
trace with debugging symbols? 

Please see http://live.gnome.org/GettingTraces for more information on how to
do so.

Thanks in advance!

Comment 18 Bruno Boaventura 2007-01-24 00:07:28 UTC

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

Comment 19 Pedro Villavicencio 2007-04-09 00:10:49 UTC

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

Comment 20 palfrey 2007-04-09 14:28:14 UTC

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

Comment 21 Damien Durand 2007-04-11 11:27:10 UTC

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

Comment 22 palfrey 2007-05-02 11:37:39 UTC

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

Comment 23 palfrey 2007-05-02 11:37:43 UTC

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

Comment 24 palfrey 2007-05-02 11:45:25 UTC

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

Comment 25 Iestyn Pryce 2007-07-24 13:51:15 UTC

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

Comment 26 palfrey 2007-09-05 17:51:57 UTC

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

Comment 27 Paolo Borelli 2007-09-21 16:22:44 UTC

all the duplicates are from version 2.16.1 and there are no dups using newer version. I am assuming this got fixed.