Bug 348848 – crashes related to slice_alloc

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 348848 - crashes related to slice_alloc


Summary:	crashes related to slice_alloc


Status:	VERIFIED NOTGNOME

Product:	glib
Classification:	Platform
Component:	general
Version:	2.12.x
Hardware:	Other All

Importance:	Normal critical
Target Milestone:	---
Assigned To:	gtkdev
QA Contact:	gtkdev

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2006-07-26 20:00 UTC by Björn Martensen
Modified:	2006-07-26 21:51 UTC

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

Description Björn Martensen 2006-07-26 20:00:00 UTC

Steps to reproduce:
1. 
2. 
3. 


Stack trace:
(gdb) bt

+ Trace 69665

#0 g_slice_alloc
from /usr/lib/libglib-2.0.so.0
#1 g_slice_alloc0
from /usr/lib/libglib-2.0.so.0
#2 g_list_alloc
from /usr/lib/libglib-2.0.so.0
#3 g_object_notify
from /usr/lib/libgobject-2.0.so.0
#4 gtk_widget_set_sensitive
from /usr/lib/libgtk-x11-2.0.so.0
#5 _gtk_action_sync_sensitive
from /usr/lib/libgtk-x11-2.0.so.0
#6 gtk_action_set_sensitive
from /usr/lib/libgtk-x11-2.0.so.0
#7 thunar_standard_view_selection_changed
at thunar-standard-view.c line 3322
#8 g_cclosure_marshal_VOID__PARAM
from /usr/lib/libgobject-2.0.so.0
#9 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#10 signal_emit_unlocked_R
from /usr/lib/libgobject-2.0.so.0
#11 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#12 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#13 g_object_dispatch_properties_changed
from /usr/lib/libgobject-2.0.so.0
#14 g_object_notify_dispatcher
from /usr/lib/libgobject-2.0.so.0
#15 g_object_thaw_notify
from /usr/lib/libgobject-2.0.so.0
#16 thunar_list_model_set_folder
at thunar-list-model.c line 1849
#17 thunar_standard_view_set_current_directory
at thunar-standard-view.c line 1169
#18 g_object_set_property
from /usr/lib/libgobject-2.0.so.0
#19 exo_bind_properties_transfer
from /opt/xfce4/lib/libexo-0.3.so.0
#20 exo_bind_properties_notify
from /opt/xfce4/lib/libexo-0.3.so.0
#21 g_cclosure_marshal_VOID__PARAM
from /usr/lib/libgobject-2.0.so.0
#22 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#23 signal_emit_unlocked_R
from /usr/lib/libgobject-2.0.so.0
#24 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#25 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#26 g_object_dispatch_properties_changed
from /usr/lib/libgobject-2.0.so.0
#27 g_object_notify_dispatcher
from /usr/lib/libgobject-2.0.so.0
#28 g_object_notify
from /usr/lib/libgobject-2.0.so.0
#29 thunar_window_set_current_directory
at thunar-window.c line 2212
#30 g_cclosure_marshal_VOID__OBJECT
from /usr/lib/libgobject-2.0.so.0
#31 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#32 signal_emit_unlocked_R
from /usr/lib/libgobject-2.0.so.0
#33 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#34 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#35 thunar_navigator_change_directory
at thunar-navigator.c line 207
#36 g_cclosure_marshal_VOID__VOID
from /usr/lib/libgobject-2.0.so.0
#37 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#38 signal_emit_unlocked_R
from /usr/lib/libgobject-2.0.so.0
#39 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#40 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#41 _gtk_action_emit_activate
from /usr/lib/libgtk-x11-2.0.so.0
#42 gtk_action_activate
from /usr/lib/libgtk-x11-2.0.so.0
#43 g_cclosure_marshal_VOID__VOID
from /usr/lib/libgobject-2.0.so.0
#44 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#45 signal_emit_unlocked_R
from /usr/lib/libgobject-2.0.so.0
#46 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#47 g_signal_emit_by_name
from /usr/lib/libgobject-2.0.so.0
#48 button_clicked
from /usr/lib/libgtk-x11-2.0.so.0
#49 g_cclosure_marshal_VOID__VOID
from /usr/lib/libgobject-2.0.so.0
#50 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#51 signal_emit_unlocked_R
from /usr/lib/libgobject-2.0.so.0
#52 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#53 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#54 gtk_button_clicked
from /usr/lib/libgtk-x11-2.0.so.0
#55 gtk_real_button_released
from /usr/lib/libgtk-x11-2.0.so.0
#56 g_cclosure_marshal_VOID__VOID
from /usr/lib/libgobject-2.0.so.0
#57 g_type_class_meta_marshal
from /usr/lib/libgobject-2.0.so.0
#58 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#59 signal_emit_unlocked_R
from /usr/lib/libgobject-2.0.so.0
#60 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#61 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#62 gtk_button_released
from /usr/lib/libgtk-x11-2.0.so.0
#63 gtk_button_button_release
from /usr/lib/libgtk-x11-2.0.so.0
#64 _gtk_marshal_BOOLEAN__BOXED
from /usr/lib/libgtk-x11-2.0.so.0
#65 g_type_class_meta_marshal
from /usr/lib/libgobject-2.0.so.0
#66 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#67 signal_emit_unlocked_R
from /usr/lib/libgobject-2.0.so.0
#68 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#69 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#70 gtk_widget_event_internal
from /usr/lib/libgtk-x11-2.0.so.0
#71 gtk_propagate_event
from /usr/lib/libgtk-x11-2.0.so.0
#72 gtk_main_do_event
from /usr/lib/libgtk-x11-2.0.so.0
#73 gdk_event_dispatch
from /usr/lib/libgdk-x11-2.0.so.0
#74 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#75 g_main_context_iterate
from /usr/lib/libglib-2.0.so.0
#76 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#77 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#78 main
at main.c line 239


Other information:
using xfce and thunar

since this happened in an unreleased testing version of thunar i don't provide the steps how to reproduce this bug but i think it's best to have the link to the mailing list where i reported crashes to benny (thunar dev) and he said this was a glib bug:

http://foo-projects.org/pipermail/thunar-dev/2006-July/003113.html

Comment 1 Owen Taylor 2006-07-26 20:03:44 UTC

Memory corruption elsewhere in the app until proved otherwise. valgrind can be
helpful in tracking down such problems.

Comment 2 Björn Martensen 2006-07-26 21:51:03 UTC

Ok, you were right. Benny fixed that issue.
Sorry