gvfsd-sftp crashed with SIGABRT in g_assertion_message()

[Filiprino]

This crash ALWAYS happens after trying to unmount an SFTP mounted folder after it's been used for some time. Using Ubuntu 14.04, fresh install.

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: gvfs-backends 1.20.1-1ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2
Uname: Linux 3.13.0-29-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
CrashCounter: 1
CurrentDesktop: Unity
Date: Wed Jun 25 22:00:25 2014
ExecutablePath: /usr/lib/gvfs/gvfsd-sftp
InstallationDate: Installed on 2014-06-05 (19 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
ProcCmdline: /usr/lib/gvfs/gvfsd-sftp --spawner :1.3 /org/gtk/gvfs/exec_spaw/9
ProcEnviron:
 XDG_RUNTIME_DIR=<set>
 SHELL=/bin/bash
 LANGUAGE=es_ES
 PATH=(custom, user)
 LANG=es_ES.UTF-8
Signal: 6
SourcePackage: gvfs
StacktraceTop:
 g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_vfs_daemon_finalize (object=0x98bb00) at gvfsdaemon.c:149
 g_object_unref () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 daemon_main (argc=argc@entry=4, argv=argv@entry=0x7fffe8e60798, max_job_threads=max_job_threads@entry=1, default_type=default_type@entry=0x410f40 "sftp", mountable_name=mountable_name@entry=0x0, first_type_name=first_type_name@entry=0x410f40 "sftp") at daemon-main.c:407
Title: gvfsd-sftp crashed with SIGABRT in g_assertion_message()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin mediatomb plugdev sambashare sudo 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 #1199787, 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.