nautilus crashed with SIGSEGV when opening a folder with many files

[Paul Greindl]

When opening a folder with around 3 500 files (about 5-10 MB each) Nautilus runs on 100 % CPU, and finally crashed when switching to list-view. After killing the main nautilus process, starting nautilus and switching to list view before entering the folder, the CPU stayed at 60-90% and it was possible to browse the files.

ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: nautilus 1:3.6.3-0ubuntu9
ProcVersionSignature: Ubuntu 3.8.0-12.21-generic 3.8.2
Uname: Linux 3.8.0-12-generic x86_64
ApportVersion: 2.9.1-0ubuntu1
Architecture: amd64
CrashCounter: 1
Date: Sat Mar 16 18:56:44 2013
Disassembly: => 0x7fbe987c6f89: Cannot access memory at address 0x7fbe987c6f89
ExecutablePath: /usr/bin/nautilus
GsettingsChanges:
 b'org.gnome.nautilus.window-state' b'geometry' b"'956x597+1431+306'"
 b'org.gnome.nautilus.window-state' b'maximized' b'true'
InstallationDate: Installed on 2013-01-21 (53 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130121)
MarkForUpload: True
ProcCmdline: nautilus -n
SegvAnalysis:
 Segfault happened at: 0x7fbe987c6f89: Cannot access memory at address 0x7fbe987c6f89
 PC (0x7fbe987c6f89) ok
 SP (0x7fff557e6d70) ok
 Reason could not be automatically determined.
Signal: 11
SourcePackage: nautilus
Stacktrace:
 #0 0x00007fbe987c6f89 in ?? ()
 No symbol table info available.
 Cannot access memory at address 0x7fff557e6d70
StacktraceTop: ?? ()
ThreadStacktrace:
 .
 Thread 6 (LWP 5085):
 #0 0x00007fbe97d6705e in ?? ()
 No symbol table info available.
 Cannot access memory at address 0x7fbe68aa2b60
Title: nautilus crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

[Apport retracing service (apport)]

Stacktrace:
 #0 0x00007fbe987c6f89 in ?? ()
 No symbol table info available.
 Cannot access memory at address 0x7fff557e6d70
StacktraceSource: #0 0x00007fbe987c6f89 in ?? ()
StacktraceTop: ?? ()
ThreadStacktrace:
 .
 Thread 6 (LWP 5085):
 #0 0x00007fbe97d6705e in ?? ()
 No symbol table info available.
 Cannot access memory at address 0x7fbe68aa2b60

[Apport retracing service (apport)]

Thank you for your report!

However, processing it in order to get sufficient information for the
developers failed (it does not generate a useful symbolic stack trace). This
might be caused by some outdated packages which were installed on your system
at the time of the report:

outdated debug symbol package for libk5crypto3: package version 1.10.1+dfsg-4+nmu1 dbgsym version 1.10.1+dfsg-4
outdated debug symbol package for libcap2: package version 1:2.22-1.2ubuntu2 dbgsym version 1:2.22-1ubuntu4
python2.7 version 2.7.3-16ubuntu2 required, but 2.7.3-16ubuntu1 is available
outdated debug symbol package for libprocps0: package version 1:3.3.3-2ubuntu5 dbgsym version 1:3.3.3-2ubuntu3
libpython2.7-minimal version 2.7.3-16ubuntu2 required, but 2.7.3-16ubuntu1 is available
outdated debug symbol package for libgssapi-krb5-2: package version 1.10.1+dfsg-4+nmu1 dbgsym version 1.10.1+dfsg-4
outdated debug symbol package for libpam-cap: package version 1:2.22-1.2ubuntu2 dbgsym version 1:2.22-1ubuntu4
outdated debug symbol package for procps: package version 1:3.3.3-2ubuntu5 dbgsym version 1:3.3.3-2ubuntu3
python2.7-minimal version 2.7.3-16ubuntu2 required, but 2.7.3-16ubuntu1 is available
outdated debug symbol package for libkrb5-3: package version 1.10.1+dfsg-4+nmu1 dbgsym version 1.10.1+dfsg-4
outdated debug symbol package for libcap2-bin: package version 1:2.22-1.2ubuntu2 dbgsym version 1:2.22-1ubuntu4
libpython2.7-stdlib version 2.7.3-16ubuntu2 required, but 2.7.3-16ubuntu1 is available
outdated debug symbol package for libkrb5support0: package version 1.10.1+dfsg-4+nmu1 dbgsym version 1.10.1+dfsg-4

Please upgrade your system to the latest package versions. If you still
encounter the crash, please file a new report.

Thank you for your understanding, and sorry for the inconvenience!