thunar crashed with SIGSEGV in g_slice_free1()

[Dan]

Ejected usb 2.0 flash drive after transferring 3.5Gb file to an exfat filesystem (using exfat-fuse I believe). May have crashed simultaneously with my pulling of the drive or an instant before. I can't seem to reproduce it.

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: thunar 1.6.3-1ubuntu4
ProcVersionSignature: Ubuntu 3.13.0-19.39-generic 3.13.6
Uname: Linux 3.13.0-19-generic x86_64
ApportVersion: 2.13.3-0ubuntu1
Architecture: amd64
CrashCounter: 1
CurrentDesktop: XFCE
Date: Sun Mar 23 20:15:16 2014
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/thunar
InstallationDate: Installed on 2014-03-03 (20 days ago)
InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140225)
ProcCmdline: Thunar --daemon
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f6b0ba65bc5: mov 0x8(%rdx),%rax
 PC (0x7f6b0ba65bc5) ok
 source "0x8(%rdx)" (0x00000008) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: thunar
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-x11-2.0.so.0
Title: thunar crashed with SIGSEGV in g_slice_free1()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo www-data

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