Bug 594914 – nautilus assert failure: *** glibc detected *** nautilus: double free or corruption - nautilus extension crash

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 594914 - nautilus assert failure: *** glibc detected *** nautilus: double free or corruption - nautilus extension crash


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


Status:	RESOLVED DUPLICATE of bug 594417

Product:	brasero
Classification:	Applications
Component:	nautilus-extension
Version:	2.27.x
Hardware:	Other Linux

Importance:	Normal critical
Target Milestone:	2.26
Assigned To:	Brasero maintainer(s)
QA Contact:	Brasero maintainer(s)

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2009-09-11 16:57 UTC by Pedro Villavicencio
Modified:	2009-09-14 17:52 UTC

See Also:
GNOME target:	---
GNOME version:	2.27/2.28

Description Pedro Villavicencio 2009-09-11 16:57:01 UTC

this report has been filed here:

https://bugs.edge.launchpad.net/ubuntu/+source/brasero/+bug/420841

"gksudo nautilus leads to apport crash report.

1) Ubuntu Karmic updated (GNOME 2.27)
2) Nautilus 1:2.27.92-0ubuntu1
3) Brasero 2.27.92-0ubuntu2
4) nautilus should run with root privileges
5) crash"

developers on the downstream report state that it might be caused by the brasero extension on nautilus

I'm asking for a valgrind log which i'll be attaching shortly.

Backtrace:

"#0  malloc_consolidate (av=<value optimized out>) at malloc.c:5089
	fb = (mfastbinptr *) 0x6a063a8
	maxfb = (mfastbinptr *) 0x6a063cc
	p = (mchunkptr) 0x6a063d0
	nextp = (mchunkptr) 0xa066b60
	unsorted_bin = (mchunkptr) 0x6a063d0
	first_unsorted = <value optimized out>
	nextchunk = (mchunkptr) 0x10a6cf30
	size = 168192864
	nextsize = <value optimized out>
	prevsize = <value optimized out>
	bck = <value optimized out>
	fwd = <value optimized out>
	__PRETTY_FUNCTION__ = "malloc_consolidate"

+ Trace 217501

#1 _int_malloc
at malloc.c line 4338
#2 _int_realloc
at malloc.c line 5224
#3 *__GI___libc_realloc
at malloc.c line 3799
#4 IA__g_realloc
at /build/buildd/glib2.0-2.21.5/glib/gmem.c line 170
#5 IA__g_quark_from_string
at /build/buildd/glib2.0-2.21.5/glib/gdataset.c line 683
#6 gst_structure_empty_new
at gststructure.c line 194
#7 gst_structure_from_string
at gststructure.c line 2037
#8 gst_caps_from_string_inplace
at gstcaps.c line 1868
#9 gst_caps_from_string
at gstcaps.c line 1906
#10 gst_registry_binary_load_plugin
at gstregistrybinary.c line 1008
#11 gst_registry_binary_read_cache
at gstregistrybinary.c line 1296
#12 ensure_current_registry
at gst.c line 938
#13 init_post
at gst.c line 1128
#14 IA__g_option_context_parse
at /build/buildd/glib2.0-2.21.5/glib/goption.c line 1947
#15 gst_init_check
at gst.c line 452
#16 brasero_burn_library_start
at burn-basics.c line 232
#17 nautilus_module_initialize
at nautilus-burn-extension.c line 933
#18 ??
#19 IA__g_type_module_use
at /build/buildd/glib2.0-2.21.5/gobject/gtypemodule.c line 257
#20 ??
#21 ??
#22 ??
#23 __libc_start_main
at libc-start.c line 220
#24 ??

Comment 1 Pedro Villavicencio 2009-09-12 17:40:58 UTC

Valgrind log:

http://launchpadlibrarian.net/31725535/valgrind.log

Comment 2 Philippe Rouquier 2009-09-14 17:52:38 UTC

Thanks for the report. I think this bug was closed just after 2.27.92 (in commit 81462010a71cd4fc5cea382c32bb9499546a224c) was released and appears to be the same as 594417. It should appear when the drive is busy while brasero tries to probe it (which is most likely the case when launching nautilus or like in the other bug).
Please test master and feel free to reopen this bug if it still does not work.

*** This bug has been marked as a duplicate of bug 594417 ***