nautilus crashed with SIGSEGV in g_slice_free1()

[Jens Kehne]

Apport appeared out of the blue. I did not notice any malfunction in Nautilus. I also don't know what triggered this and therefore cannot reproduce it.
Opening a new bug as requested in #176181.

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: nautilus 1:3.8.2-0ubuntu2.1
Uname: Linux 3.12.2-zen+ x86_64
ApportVersion: 2.12.5-0ubuntu2.1
Architecture: amd64
Date: Wed Dec 4 10:36:03 2013
ExecutablePath: /usr/bin/nautilus
GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' b"'832x550+0+59'"
InstallationDate: Installed on 2012-06-05 (546 days ago)
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425)
MarkForUpload: True
ProcCmdline: nautilus -n
ProcEnviron:
 SHELL=/usr/bin/fish
 PATH=(custom, user)
 LANG=de_DE.UTF-8
 LANGUAGE=de_DE:en
 XDG_RUNTIME_DIR=<set>
SegvAnalysis:
 Segfault happened at: 0x7f28e23482d9: mov 0x8(%rax),%rdi
 PC (0x7f28e23482d9) ok
 source "0x8(%rax)" (0x00000008) not located in a known VMA region (needed readable region)!
 destination "%rdi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: nautilus
StacktraceTop:
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_slice_free1 () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_type_free_instance () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
Title: nautilus crashed with SIGSEGV in g_slice_free1()
UpgradeStatus: Upgraded to saucy on 2013-10-26 (38 days ago)
UserGroups: adm cdrom dialout dip kvm libvirtd lpadmin plugdev sambashare src sudo tracing vboxusers wireshark

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1196063, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.