thunar crashed with SIGSEGV in g_slice_free1()

[Uncle Spellbinder]

This incident occurred when closing Thunar after moving a file from my PC hard drive to my external drive. The cut/paste operation was complete, I clicked the "X" to close Thunar and got the "Ubuntu experienced an error" message.

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: thunar 1.6.3-1ubuntu1
ProcVersionSignature: Ubuntu 3.11.0-7.14-generic 3.11.1
Uname: Linux 3.11.0-7-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 2.12.4-0ubuntu1
Architecture: amd64
Date: Sat Sep 21 13:33:04 2013
ExecutablePath: /usr/bin/thunar
InstallationDate: Installed on 2013-09-18 (3 days ago)
InstallationMedia: Xubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130818)
MarkForUpload: True
ProcCmdline: Thunar --daemon
SegvAnalysis:
 Segfault happened at: 0x7fd86f1b3405: mov 0x8(%rdx),%rax
 PC (0x7fd86f1b3405) 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 cdrom dip lpadmin plugdev sambashare sudo

[Uncle Spellbinder (spellbinder)]

Sorry. Forgot to add (though I know it's in the crash info)...

Xubuntu 13.10, 64 bit.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[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.