Bug 692182 – nautilus assert failure: *** glibc detected *** nautilus: double free or corruption (fasttop): 0x000000000178d9c0 ***

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 692182 - nautilus assert failure: *** glibc detected *** nautilus: double free or corruption (fasttop): 0x000000000178d9c0 ***


Summary:	nautilus assert failure: * glibc detected * nautilus: double free or corr...


Status:	RESOLVED WONTFIX

Product:	gtk+
Classification:	Platform
Component:	Widget: Other
Version:	3.6.x
Hardware:	Other Linux

Importance:	Normal normal
Target Milestone:	---
Assigned To:	gtk-bugs
QA Contact:	gtk-bugs

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2013-01-21 09:40 UTC by Cristian Aravena Romero
Modified:	2015-05-10 05:43 UTC

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

Description Cristian Aravena Romero 2013-01-21 09:40:18 UTC

Reboot nautilus and crash:

ProblemType: Crash
Architecture: amd64
CrashCounter: 1
Date: Sun Jan 20 21:07:31 2013
DistroRelease: Ubuntu 13.04
ExecutablePath: /usr/bin/nautilus
ExecutableTimestamp: 1358220911
ProcCmdline: nautilus
ProcCwd: /home/caravena
ProcEnviron:
 LANGUAGE=es_CL:zh_CN:es_ES:en
 LC_TIME=es_CL.UTF-8
 LC_MONETARY=es_CL.UTF-8
 PATH=(custom, user)
 LC_ADDRESS=es_CL.UTF-8
 XDG_RUNTIME_DIR=<set>
 LANG=es_CL.UTF-8
 LC_TELEPHONE=es_CL.UTF-8
 SHELL=/bin/bash
 LC_NAME=es_CL.UTF-8
 LC_MEASUREMENT=es_CL.UTF-8
 LC_NUMERIC=es_CL.UTF-8
 LC_PAPER=es_CL.UTF-8


Stacktrace:

+ Trace 231405

#0 __GI_raise
at ../nptl/sysdeps/unix/sysv/linux/raise.c line 63
#1 __GI_abort
at abort.c line 90
#2 __libc_message
at ../sysdeps/unix/sysv/linux/libc_fatal.c line 200
#3 malloc_printerr
#4 _int_free
at malloc.c line 3821
#5 _XEventsQueued
from /usr/lib/x86_64-linux-gnu/libX11.so.6
#6 XPending
from /usr/lib/x86_64-linux-gnu/libX11.so.6
#7 _gdk_x11_display_queue_events
at /build/buildd/gtk+3.0-3.6.4/./gdk/x11/gdkeventsource.c line 318
#8 gdk_display_get_event
at /build/buildd/gtk+3.0-3.6.4/./gdk/gdkdisplay.c line 310
#9 gdk_event_source_dispatch
at /build/buildd/gtk+3.0-3.6.4/./gdk/x11/gdkeventsource.c line 354
#10 g_main_dispatch
at /build/buildd/glib2.0-2.35.4/./glib/gmain.c line 2784
#11 g_main_context_dispatch
at /build/buildd/glib2.0-2.35.4/./glib/gmain.c line 3288
#12 g_main_context_iterate
at /build/buildd/glib2.0-2.35.4/./glib/gmain.c line 3359
#13 g_main_context_iteration
at /build/buildd/glib2.0-2.35.4/./glib/gmain.c line 3420
#14 g_application_run
at /build/buildd/glib2.0-2.35.4/./gio/gapplication.c line 1620
#15 main
at nautilus-main.c line 103

Comment 1 Cristian Aravena Romero 2013-01-21 09:44:29 UTC

1:3.6.3-0ubuntu5

Comment 2 Cosimo Cecchi 2013-01-21 14:59:52 UTC

-> gtk+

Looks like a crash in GTK.

Comment 3 Matthias Clasen 2015-05-10 05:43:21 UTC

Sadly, too much time has passed to track this down