Bug 711239 – nautilus segfaults in g_slice_free1()

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 711239 - nautilus segfaults in g_slice_free1()


Summary:	nautilus segfaults in g_slice_free1()


Status:	RESOLVED OBSOLETE

Product:	nautilus
Classification:	Core
Component:	Crashers
Version:	3.8.x
Hardware:	Other Linux

Importance:	Normal critical
Target Milestone:	---
Assigned To:	Nautilus Maintainers
QA Contact:	Nautilus Maintainers

URL:
Whiteboard:

Duplicates:	728090 (view as bug list)
Depends on:
Blocks:

Reported:	2013-11-01 01:00 UTC by Sebastien Bacher
Modified:	2021-06-18 15:29 UTC

See Also:
GNOME target:	---
GNOME version:	---

Description Sebastien Bacher 2013-11-01 01:00:55 UTC

The bug has been reported https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1196063

The bug has quite some duplicates but there is no consistent steps to trigger the issue

nautilus 3.8.2 stacktrace 

"#0  0x00007f3bdd2642c9 in magazine_chain_pop_head (magazine_chunks=<synthetic pointer>) at /build/buildd/glib2.0-2.38.0/./glib/gslice.c:550
        chunk = 0x2481930

+ Trace 232693

#1 magazine_chain_prepare_fields
at /build/buildd/glib2.0-2.38.0/./glib/gslice.c line 623
#2 magazine_cache_push_magazine
at /build/buildd/glib2.0-2.38.0/./glib/gslice.c line 697
#3 thread_memory_magazine2_unload
at /build/buildd/glib2.0-2.38.0/./glib/gslice.c line 815
#4 g_slice_free1
at /build/buildd/glib2.0-2.38.0/./glib/gslice.c line 1106
#5 g_type_free_instance
at /build/buildd/glib2.0-2.38.0/./gobject/gtype.c line 1938
#6 gtk_tree_view_remove_column
at /build/buildd/gtk+3.0-3.8.4/./gtk/gtktreeview.c line 12022
#7 gtk_tree_view_destroy
at /build/buildd/gtk+3.0-3.8.4/./gtk/gtktreeview.c line 2051
#8 g_closure_invoke
at /build/buildd/glib2.0-2.38.0/./gobject/gclosure.c line 777
#9 signal_emit_unlocked_R
at /build/buildd/glib2.0-2.38.0/./gobject/gsignal.c line 3702
#10 g_signal_emit_valist
at /build/buildd/glib2.0-2.38.0/./gobject/gsignal.c line 3330
#11 g_signal_emit
at /build/buildd/glib2.0-2.38.0/./gobject/gsignal.c line 3386
#12 gtk_widget_dispose
at /build/buildd/gtk+3.0-3.8.4/./gtk/gtkwidget.c line 10771
#13 g_object_run_dispose
at /build/buildd/glib2.0-2.38.0/./gobject/gobject.c line 1067
#14 gtk_scrolled_window_forall
at /build/buildd/gtk+3.0-3.8.4/./gtk/gtkscrolledwindow.c line 1582
#15 gtk_container_destroy
at /build/buildd/gtk+3.0-3.8.4/./gtk/gtkcontainer.c line 1377
#16 g_closure_invoke
at /build/buildd/glib2.0-2.38.0/./gobject/gclosure.c line 777
#17 signal_emit_unlocked_R
at /build/buildd/glib2.0-2.38.0/./gobject/gsignal.c line 3702
#18 g_signal_emit_valist
at /build/buildd/glib2.0-2.38.0/./gobject/gsignal.c line 3330
#19 g_signal_emit
at /build/buildd/glib2.0-2.38.0/./gobject/gsignal.c line 3386
#20 gtk_widget_dispose
at /build/buildd/gtk+3.0-3.8.4/./gtk/gtkwidget.c line 10771
#21 g_object_run_dispose
at /build/buildd/glib2.0-2.38.0/./gobject/gobject.c line 1067
#22 gtk_box_forall
at /build/buildd/gtk+3.0-3.8.4/./gtk/gtkbox.c line 1865
#23 gtk_container_destroy
at /build/buildd/gtk+3.0-3.8.4/./gtk/gtkcontainer.c line 1377
#24 g_closure_invoke
at /build/buildd/glib2.0-2.38.0/./gobject/gclosure.c line 777
#25 signal_emit_unlocked_R
at /build/buildd/glib2.0-2.38.0/./gobject/gsignal.c line 3702
#26 g_signal_emit_valist
at /build/buildd/glib2.0-2.38.0/./gobject/gsignal.c line 3330
#27 g_signal_emit
at /build/buildd/glib2.0-2.38.0/./gobject/gsignal.c line 3386
#28 gtk_widget_dispose
at /build/buildd/gtk+3.0-3.8.4/./gtk/gtkwidget.c line 10771
#29 g_object_run_dispose
at /build/buildd/glib2.0-2.38.0/./gobject/gobject.c line 1067
#30 gtk_widget_destroy
at /build/buildd/gtk+3.0-3.8.4/./gtk/gtkwidget.c line 4093
#31 nautilus_window_tear_down_sidebar
at nautilus-window.c line 558
#32 nautilus_window_destroy
at nautilus-window.c line 1253
#33 g_closure_invoke
at /build/buildd/glib2.0-2.38.0/./gobject/gclosure.c line 777
#34 signal_emit_unlocked_R
at /build/buildd/glib2.0-2.38.0/./gobject/gsignal.c line 3702
#35 g_signal_emit_valist
at /build/buildd/glib2.0-2.38.0/./gobject/gsignal.c line 3330
#36 g_signal_emit
at /build/buildd/glib2.0-2.38.0/./gobject/gsignal.c line 3386
#37 gtk_widget_dispose
at /build/buildd/gtk+3.0-3.8.4/./gtk/gtkwidget.c line 10771
#38 g_object_run_dispose
at /build/buildd/glib2.0-2.38.0/./gobject/gobject.c line 1067
#39 nautilus_window_delete_event
at nautilus-window.c line 1779
#40 _gtk_marshal_BOOLEAN__BOXEDv
at /build/buildd/gtk+3.0-3.8.4/./gtk/gtkmarshalers.c line 130
#41 _g_closure_invoke_va
at /build/buildd/glib2.0-2.38.0/./gobject/gclosure.c line 840
#42 g_signal_emit_valist
at /build/buildd/glib2.0-2.38.0/./gobject/gsignal.c line 3238
#43 g_signal_emit
at /build/buildd/glib2.0-2.38.0/./gobject/gsignal.c line 3386
#44 gtk_widget_event_internal
at /build/buildd/gtk+3.0-3.8.4/./gtk/gtkwidget.c line 6714
#45 gtk_widget_event
at /build/buildd/gtk+3.0-3.8.4/./gtk/gtkwidget.c line 6371
#46 gtk_main_do_event
at /build/buildd/gtk+3.0-3.8.4/./gtk/gtkmain.c line 1592
#47 gdk_event_source_dispatch
at /build/buildd/gtk+3.0-3.8.4/./gdk/x11/gdkeventsource.c line 364
#48 g_main_dispatch
at /build/buildd/glib2.0-2.38.0/./glib/gmain.c line 3065
#49 g_main_context_dispatch
at /build/buildd/glib2.0-2.38.0/./glib/gmain.c line 3641
#50 g_main_context_iterate
at /build/buildd/glib2.0-2.38.0/./glib/gmain.c line 3712
#51 g_main_context_iteration
at /build/buildd/glib2.0-2.38.0/./glib/gmain.c line 3773
#52 g_application_run
at /build/buildd/glib2.0-2.38.0/./gio/gapplication.c line 1635

Comment 1 Christian Persch 2013-11-02 11:58:55 UTC

Crashes in the allocator usually indicate memory corruption that happened earlier. Can you get a valgrind log?

Comment 2 heresomename 2014-03-14 11:44:04 UTC

Got the same stacktrace browsing a folder with 450 mp3 files with thumbnails.
I doubt there is a possibility to get valgrind log cause the crash was quite spontaneous. I had browsed the same folder earlier and there was no crash.
nautilus 3.10.2.

Comment 3 Jussi Saarinen 2014-04-12 21:39:57 UTC

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

Comment 4 Jussi Saarinen 2014-04-12 21:41:54 UTC

I can confirm this bug. My backtraces can be found in the duplicate report.

Comment 5 Jussi Saarinen 2014-04-19 09:23:15 UTC

I managed to get a valgrind log. Hope it helps.

https://drive.google.com/file/d/0B4VU-cbutMY3aXM1MWhybk9MTGc/edit?usp=sharing

Comment 6 André Klapper 2021-06-18 15:29:45 UTC

GNOME is going to shut down bugzilla.gnome.org in favor of gitlab.gnome.org.
As part of that, we are mass-closing older open tickets in bugzilla.gnome.org
which have not seen updates for a longer time (resources are unfortunately
quite limited so not every ticket can get handled).

If you can still reproduce the situation described in this ticket in a recent
and supported software version of Files (nautilus), then please follow
  https://wiki.gnome.org/GettingInTouch/BugReportingGuidelines
and create a new ticket at
  https://gitlab.gnome.org/GNOME/nautilus/-/issues/

Thank you for your understanding and your help.