gvfsd-trash crashed with signal 5 in _g_dbus_oom()

[dmiranda]

Crashed when openning the trash folder (with 1000+ files)

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: gvfs-daemons 1.10.1-1ubuntu2
ProcVersionSignature: Ubuntu 3.2.0-10.18-generic 3.2.1
Uname: Linux 3.2.0-10-generic i686
NonfreeKernelModules: btrfs zlib_deflate libcrc32c ufs qnx4 hfsplus hfs minix ntfs msdos jfs xfs reiserfs ext2 nls_iso8859_1 nls_cp437 vfat fat bnep rfcomm bluetooth binfmt_misc snd_hda_codec_realtek arc4 rtl8187 mac80211 snd_hda_intel i915 snd_hda_codec joydev cfg80211 usbhid drm_kms_helper eeprom_93cx6 drm snd_hwdep snd_pcm hid snd_seq_midi snd_rawmidi snd_seq_midi_event snd_seq snd_timer snd_seq_device snd i2c_algo_bit video mac_hid serio_raw ppdev parport_pc soundcore snd_page_alloc lp parport usb_storage atl2
ApportVersion: 1.91-0ubuntu1
Architecture: i386
Date: Sat Jan 28 19:46:15 2012
ExecutablePath: /usr/lib/gvfs/gvfsd-trash
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
ProcCmdline: /usr/lib/gvfs/gvfsd-trash --spawner :1.1 /org/gtk/gvfs/exec_spaw/0
Signal: 5
SourcePackage: gvfs
StacktraceTop:
 _g_dbus_oom () from /usr/lib/i386-linux-gnu/gvfs/libgvfscommon.so
 _g_dbus_append_file_attribute () from /usr/lib/i386-linux-gnu/gvfs/libgvfscommon.so
 _g_dbus_append_file_info () from /usr/lib/i386-linux-gnu/gvfs/libgvfscommon.so
 g_vfs_job_enumerate_add_info () from /usr/lib/i386-linux-gnu/gvfs/libgvfsdaemon.so
 ?? ()
Title: gvfsd-trash crashed with signal 5 in _g_dbus_oom()
UpgradeStatus: Upgraded to precise on 2012-01-23 (5 days ago)
UserGroups: adm admin audio cdrom dialout dip fax floppy fuse lpadmin netdev plugdev sambashare scanner tape video

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