nautilus crashed with SIGSEGV in malloc()

[Edward Donovan]

Lots of nautilus crashes lately, for me, in Raring. Like bug 1101965 and bug 1101985. This appears to be a separate point in the code, but we'll see.

I removed .xsession-errors, because it had directory and other info from my machine. The possibly relevant part was the last two lines:

(process:10001): GLib-CRITICAL **: g_slice_set_config: assertion `sys_page_size == 0' failed
(nautilus:8538): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed

I'm not sure if these came right at the time of the crash.

Thanks.

ProblemType: CrashDistroRelease: Ubuntu 13.04
Package: nautilus 1:3.6.3-0ubuntu5
ProcVersionSignature: Ubuntu 3.7.0-7.5-lowlatency 3.7.0
Uname: Linux 3.7.0-7-lowlatency x86_64
ApportVersion: 2.8-0ubuntu2
Architecture: amd64
CrashCounter: 1
Date: Wed Jan 23 20:09:18 2013
ExecutablePath: /usr/bin/nautilus
GsettingsChanges:
 b'org.gnome.nautilus.window-state' b'geometry' b"'927x1019+65+24'"
 b'org.gnome.nautilus.window-state' b'maximized' b'true'
 b'org.gnome.nautilus.window-state' b'sidebar-width' b'143'
MarkForUpload: True
ProcCmdline: nautilus
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f6be267cc96: mov 0x10(%r14),%r8
 PC (0x7f6be267cc96) ok
 source "0x10(%r14)" (0x00000011) not located in a known VMA region (needed readable region)!
 destination "%r8" ok
SegvReason: reading NULL VMASignal: 11SourcePackage: nautilus
StacktraceTop:
 ?? () from /lib/x86_64-linux-gnu/libc.so.6
 malloc () from /lib/x86_64-linux-gnu/libc.so.6
 cairo_region_create_rectangle () from /usr/lib/x86_64-linux-gnu/libcairo.so.2
 ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
 gtk_widget_queue_draw_area () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
Title: nautilus crashed with SIGSEGV in malloc()
UpgradeStatus: Upgraded to raring on 2012-06-14 (223 days ago)
UserGroups: adm cdrom dip lpadmin nopasswdlogin plugdev sambashare sudo

[Sebastien Bacher (seb128)]

The bug didn't get activity/new duplicates for some years and the nautilus code saw quite some changes since which probably deprecated the issue so closing it. If it's still a problem in recent Ubuntu/nautilus version please submit a new report