nautilus crashed with SIGSEGV in g_cclosure_marshal_VOID__VOID()

[Jānis Kangarooo]

2nd time already i move or delete files in Nautulis in 1TB fat drive.
It has folders with 2000 and 25000 files.
In 2000 i moved inside folders to sub level and crashed but couldnt get crash couse of some error it said.
In 25000 files i deleted just 100 files and it crashed and gave this error.

Did it finished moving files in 2000 file folder or are they lost couse i now folder from witch i moved all files is empty as it should have been if all file moving was without crash alos..

ProblemType: Crash
DistroRelease: Ubuntu 10.04
Package: nautilus 1:2.30.1-0ubuntu1.2
ProcVersionSignature: Ubuntu 2.6.32-45.101-generic 2.6.32.60+drm33.26
Uname: Linux 2.6.32-45-generic i686
Architecture: i386
CrashCounter: 1
Date: Wed Dec 26 00:43:17 2012
ExecutablePath: /usr/bin/nautilus
InstallationMedia: Ubuntu-Netbook 10.04 "Lucid Lynx" - Release i386 (20100429.4)
ProcCmdline: nautilus
ProcEnviron:
 LANGUAGE=en_US:en
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x811d8a1: mov 0xc(%eax),%edx
 PC (0x0811d8a1) ok
 source "0xc(%eax)" (0x0000000c) not located in a known VMA region (needed readable region)!
 destination "%edx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: nautilus
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 g_cclosure_marshal_VOID__VOID ()
 g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
Title: nautilus crashed with SIGSEGV in g_cclosure_marshal_VOID__VOID()
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare 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 #968473, 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.