nautilus crashed with SIGSEGV in g_main_context_dispatch() (while showing a file that's being changed)

[DorianDaumiller]

nautlius open in two-pane mode.
crash happened when i entered a directory, in which a file just changed (i.e. a download folder)

does not happen regularly though.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: nautilus 1:3.1.90-0ubuntu3
ProcVersionSignature: Ubuntu 3.0.0-11.17-generic-pae 3.0.4
Uname: Linux 3.0.0-11-generic-pae i686
ApportVersion: 1.23-0ubuntu1
Architecture: i386
Date: Sun Sep 18 13:42:15 2011
ExecutablePath: /usr/bin/nautilus
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
ProcCmdline: nautilus -n
ProcEnviron:
 LANGUAGE=de_DE:de:en_GB:en
 PATH=(custom, user)
 LANG=de_DE.utf8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x810eb0d: mov 0x308(%eax),%eax
 PC (0x0810eb0d) ok
 source "0x308(%eax)" (0xaaaaadb2) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: nautilus
StacktraceTop:
 ?? ()
 ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
 g_main_context_dispatch () from /lib/i386-linux-gnu/libglib-2.0.so.0
 ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
 g_main_loop_run () from /lib/i386-linux-gnu/libglib-2.0.so.0
Title: nautilus crashed with SIGSEGV in g_main_context_dispatch()
UpgradeStatus: Upgraded to oneiric on 2011-09-14 (3 days ago)
UserGroups: adm admin audio cdrom dialout lpadmin netdev plugdev sambashare

[DorianDaumiller (dorian-daumiller)]

view was ctrl-2 ("list")

[DorianDaumiller (dorian-daumiller)]

just crashed again (in the same directory)

this time i tried to select multiple files using the keyboard (shift-up after clicking a file to be specific).

After opening the dir again, this works.

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #849473, 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.