thunar crashed with SIGSEGV

[Jackson Doak]

Closing thunar after a 1gb folder was copied causes this error

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: thunar 1.6.3-1ubuntu3
ProcVersionSignature: Ubuntu 3.13.0-11.31-generic 3.13.3
Uname: Linux 3.13.0-11-generic x86_64
ApportVersion: 2.13.2-0ubuntu5
Architecture: amd64
CrashCounter: 1
CurrentDesktop: XFCE
Date: Mon Feb 24 08:06:10 2014
ExecutablePath: /usr/bin/thunar
InstallationDate: Installed on 2013-12-17 (68 days ago)
InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20131217)
ProcCmdline: Thunar --sm-client-id 2632e7b0b-3110-42fb-866d-af1c9d2246fd --daemon
ProcEnviron:
 LANGUAGE=en_AU:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_AU.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7fd874675bb9: mov 0x8(%rax),%rdi
 PC (0x7fd874675bb9) 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: thunar
Stacktrace:
 #0 0x00007fd874675bb9 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 No symbol table info available.
 Cannot access memory at address 0x7fff3040db48
StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
Title: thunar crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm autopilot cdrom dip lpadmin plugdev sambashare sudo

[Apport retracing service (apport)]

StacktraceTop:
 magazine_chain_pop_head (magazine_chunks=<synthetic pointer>) at /build/buildd/glib2.0-2.39.90/./glib/gslice.c:544
 magazine_chain_prepare_fields (magazine_chunks=0x0) at /build/buildd/glib2.0-2.39.90/./glib/gslice.c:617
 magazine_cache_push_magazine (ix=11, ix@entry=<error reading variable: Cannot access memory at address 0x7fff3040db48>, magazine_chunks=0x7fd879fbecb0, count=8) at /build/buildd/glib2.0-2.39.90/./glib/gslice.c:691

[Launchpad Janitor (janitor)]

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

[Sean Davis (bluesabre)]

Seems likely to be a one-off crash. Closing this issue out.