nautilus crashed with SIGSEGV in g_slice_free1()

[Colin Law]

Possibly co-incident with unmounting a Nexus 7 on USB (via right click on icon in launcher) and unplugging.

ProblemType: Crash
DistroRelease: Ubuntu 15.04
Package: nautilus 1:3.14.2-0ubuntu4
ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5
Uname: Linux 3.18.0-13-generic x86_64
ApportVersion: 2.16.1-0ubuntu2
Architecture: amd64
CurrentDesktop: Unity
Date: Thu Feb 26 16:17:43 2015
ExecutablePath: /usr/bin/nautilus
GsettingsChanges:
 b'org.gnome.nautilus.list-view' b'default-visible-columns' b"['name', 'size', 'date_modified']"
 b'org.gnome.nautilus.list-view' b'default-zoom-level' b"'smaller'"
 b'org.gnome.nautilus.list-view' b'use-tree-view' b'true'
 b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'type', 'size', 'date_modified', 'owner', 'group', 'permissions', 'mime_type', 'where', 'date_accessed']"
InstallationDate: Installed on 2014-10-21 (128 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20141017)
ProcCmdline: nautilus -n
ProcEnviron:
 LANGUAGE=en_GB:en
 PATH=(custom, user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f8e69bd67ee: mov (%r8),%r9
 PC (0x7f8e69bd67ee) ok
 source "(%r8)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%r9" 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
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
Title: nautilus crashed with SIGSEGV in g_slice_free1()
UpgradeStatus: Upgraded to vivid on 2015-02-25 (0 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

[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 #1424204, 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.