nautilus crash in g_closure_invoke

[Martin Pool]

Binary package hint: nautilus

Because of bug 385009 I don't have a great apport report on this.

Nautilus is crashing fairly often for me in Karmic. One typical manually captured traceback looks like this:

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xb8052760 (LWP 12935)]
0x00000000 in ?? ()
(gdb) bt
#0 0x00000000 in ?? ()
#1 0x0029d749 in ?? () from /usr/lib/libgobject-2.0.so.0
#2 0x0029f0c2 in g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
#3 0x002b579b in ?? () from /usr/lib/libgobject-2.0.so.0
#4 0x002b6d48 in g_signal_emit_valist () from /usr/lib/libgobject-2.0.so.0
#5 0x002b7346 in g_signal_emit () from /usr/lib/libgobject-2.0.so.0
#6 0x0113648e in ?? () from /usr/lib/libgtk-x11-2.0.so.0
#7 0x00ffabd0 in gtk_propagate_event () from /usr/lib/libgtk-x11-2.0.so.0
#8 0x00ffbffa in gtk_main_do_event () from /usr/lib/libgtk-x11-2.0.so.0
#9 0x0093c25a in ?? () from /usr/lib/libgdk-x11-2.0.so.0
#10 0x007f9ad8 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#11 0x007fd070 in ?? () from /usr/lib/libglib-2.0.so.0
#12 0x007fd4df in g_main_loop_run () from /usr/lib/libglib-2.0.so.0
#13 0x00ffc619 in gtk_main () from /usr/lib/libgtk-x11-2.0.so.0
#14 0x08080a39 in main (argc=1, argv=0xbfca5074) at nautilus-main.c:524

ProblemType: Bug
Architecture: i386
Date: Tue Jun 9 11:22:07 2009
DistroRelease: Ubuntu 9.10
Package: nautilus 1:2.27.1-0ubuntu1
ProcEnviron:
 PATH=(custom, user)
 LANG=en_AU.UTF-8
 SHELL=/bin/zsh
ProcVersionSignature: Ubuntu 2.6.30-8.9-generic
SourcePackage: nautilus
Uname: Linux 2.6.30-8-generic i686

[Martin Pool (mbp)]

Here is a better traceback

(gdb) bt full
#0 0x00000000 in ?? ()
No symbol table info available.
#1 0x00b03749 in g_type_class_meta_marshal (closure=0xa1691a8, return_value=0xbfd78334, n_param_values=2, param_values=0xbfd78334, invocation_hint=0xbfd78320, marshal_data=0xb0) at /build/buildd/glib2.0-2.21.1/gobject/gclosure.c:878
 callback = <value optimized out>
#2 0x00b050c2 in IA__g_closure_invoke (closure=0x9d83bf0, return_value=0xbfd78334, n_param_values=2, param_values=0xa25b0c8, invocation_hint=0xbfd78320) at /build/buildd/glib2.0-2.21.1/gobject/gclosure.c:767
 marshal = (GClosureMarshal) 0xb03700 <g_type_class_meta_marshal>
 marshal_data = (gpointer) 0xb0
 __PRETTY_FUNCTION__ = "IA__g_closure_invoke"
#3 0x00b1b79b in signal_emit_unlocked_R (node=<value optimized out>, detail=<value optimized out>, instance=0xa1691a8, emission_return=0xbfd7847c, instance_and_params=0xa25b0c8) at /build/buildd/glib2.0-2.21.1/gobject/gsignal.c:3285
 accumulator = (SignalAccumulator *) 0x9d83da8
 emission = {next = 0x0, instance = 0xa1691a8, ihint = {signal_id = 30, detail = 0, run_type = G_SIGNAL_RUN_LAST}, state = EMISSION_RUN, chain_type = 165279968}
 class_closure = (GClosure *) 0x9d83bf0
 handler_list = (Handler *) 0x0
 return_accu = <value optimized out>
 accu = {g_type = 20, data = {{v_int = 0, v_uint = 0, v_long = 0, v_ulong = 0, v_int64 = 0, v_uint64 = 0, v_float = 0, v_double = 0, v_pointer = 0x0}, {v_int = 0, v_uint = 0, v_long = 0, v_ulong = 0, v_int64 = 0, v_uint64 = 0, v_float = 0, v_double = 0, v_pointer = 0x0}}}
 signal_id = 30
 max_sequential_handler_number = 13191
 return_value_altered = 0
#4 0x00b1cd48 in IA__g_signal_emit_valist (instance=0xa1691a8, signal_id=30, detail=0, var_args=0xbfd784e0 "\f\205׿\003") at /build/buildd/glib2.0-2.21.1/gobject/gsignal.c:2990
 return_value = {g_type = 20, data = {{v_int = 0, v_uint = 0, v_long = 0, v_ulong = 0, v_int64 = 0, v_uint64 = 0, v_float = 0, v_double = 0, v_pointer = 0x0}, {v_int = 0, v_uint = 0, v_long = 0, v_ulong = 0, v_int64 = 0, v_uint64 = 0, v_float = 0, v_double = 0, v_pointer = 0x0}}}
 error = <value optimized out>
 signal_return_type = 20
 node = (SignalNode *) 0x9d83d60
 i = <value optimized out>
 n_params = 1
 __PRETTY_FUNCTION__ = "IA__g_signal_emit_valist"
#5 0x00b1d346 in IA__g_signal_emit (instance=0xa1691a8, signal_id=30, detail=0) at /build/buildd/glib2.0-2.21.1/gobject/gsignal.c:3037
No locals.
#6 0x0106b48e in gtk_widget_event_internal (widget=<value optimized out>, event=0xb763d2d0) at /build/buildd/gtk+2.0-2.17.0/gtk/gtkwidget.c:4761
 signal_num = <value optimized out>
 return_val = 0
#7 0x00f2fbd0 in IA__gtk_propagate_event (widget=0xa1691a8, event=0xb763d2d0) at /build/buildd/gtk+2.0-2.17.0/gtk/gtkmain.c:2396
 tmp = (GtkWidget *) 0xa1691a8
 handled_event = <value optimized out>
 __PRETTY_FUNCTION__ = "IA__gtk_propagate_event"
#8 0x00f30ffa in IA__gtk_main_do_event (event=0xb763d2d0) at /build/buildd/gtk+2.0-2.17.0/gtk/gtkmain.c:1601
 event_widget = (GtkWidget *) 0x9f3a2a0
 grab_widget = <value optimized out>
 window_group = (GtkWindowGroup *) 0x9f1ec50
 rewritten_event = (GdkEvent *) 0x0
 tmp_list = <value optimized out>
 __PRETTY_FUNCTION__ = "IA__gtk_main_do_e...

[Sebastien Bacher (seb128)]

Could you try to describe what you were doing when it crashed?

[Sebastien Bacher (seb128)]

Could you try to describe what you were doing when it crashed? Did the issue started recently? Could you try to get a valgrind log too?

[Martin Pool (mbp)]

2009/6/9 Sebastien Bacher <email address hidden>:
> Could you try to describe what you were doing when it crashed? Did the
> issue started recently? Could you try to get a valgrind log too?

Yes, it's just started in the last couple of days. It was not
happening at UDS, and then I updated my machine on Friday when I got
home.

It's happened several times in using nautilus for a few minutes. I
can't work out any single action that makes it happen, but I have
been:

* pressing Ctrl-L to enter a path
* scrolling through a window
* clicking on a path component button
* resizing a nautilus window

I'll try to run Valgrind tomorrow.

--
Martin <http://launchpad.net/~mbp/>

[Martin Pool (mbp)]

It crashed again today on clicking the View menu. Unfortunately I wasn't running it under Valgrind at the time.

[Pedro Villavicencio (pedro)]

Hello Martin, Are you still facing this? any luck with the valgrind log? do you have some easy steps in order to recreate this crash? Thanks in advance.

[Martin Pool (mbp)]

2009/7/31 Pedro Villavicencio <email address hidden>:
> Hello Martin, Are you still facing this? any luck with the valgrind log?
> do you have some easy steps in order to recreate this crash? Thanks in
> advance.

I haven't seen it recently, and I haven't reproduced it when running
under Valgrind.

--
Martin <http://launchpad.net/~mbp/>

[Martin Mai (mrkanister-deactivatedaccount-deactivatedaccount)]

Thanks. Closing the bug then.