Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 225088 - nautilus goes to 100% cpu displaying a folder
Summary: nautilus goes to 100% cpu displaying a folder
Alias: None
Product: Fedora
Classification: Fedora
Component: nautilus
Version: 6
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Tomáš Bžatek
QA Contact:
Whiteboard: bzcl34nup
Depends On:
TreeView+ depends on / blocked
Reported: 2007-01-28 21:22 UTC by Herbert Carl Meyer
Modified: 2015-03-03 22:31 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2008-05-06 19:06:55 UTC

Attachments (Terms of Use)

Description Herbert Carl Meyer 2007-01-28 21:22:44 UTC
Description of problem:
nautilus goes to 100% cpu displaying a folder

Version-Release number of selected component (if applicable):

How reproducible:
on a particular folder, 100%. No problem with other folders (so far).

Steps to Reproduce:
1. open a nautilus file brower
2. attempt to browse /extra/hcmeyer/MathPublications
Actual results:
nautilus goes to 100%cpu, never displays folder.

Expected results:
display files and folders in folder

Additional info:
originally occured this AM when folder was renamed. I thought it was cache
problems caused by rename, but system has been rebooted since, still occurs.
Contents of folder are .pdf's perhaps problems with preview.

Comment 1 Alexander Larsson 2007-04-11 15:20:06 UTC
Any chance you could try to figure out which file is causing the problem?
I.e. move half the files to another directory and see which directory doesn't
work, then repeat this on the smaller directory.

Comment 2 Bug Zapper 2008-04-04 05:46:29 UTC
Fedora apologizes that these issues have not been resolved yet. We're
sorry it's taken so long for your bug to be properly triaged and acted
on. We appreciate the time you took to report this issue and want to
make sure no important bugs slip through the cracks.

If you're currently running a version of Fedora Core between 1 and 6,
please note that Fedora no longer maintains these releases. We strongly
encourage you to upgrade to a current Fedora release. In order to
refocus our efforts as a project we are flagging all of the open bugs
for releases which are no longer maintained and closing them.

If this bug is still open against Fedora Core 1 through 6, thirty days
from now, it will be closed 'WONTFIX'. If you can reporduce this bug in
the latest Fedora version, please change to the respective version. If
you are unable to do this, please add a comment to this bug requesting
the change.

Thanks for your help, and we apologize again that we haven't handled
these issues to this point.

The process we are following is outlined here:

We will be following the process here: to ensure this
doesn't happen again.

And if you'd like to join the bug triage team to help make things
better, check out

Comment 3 Bug Zapper 2008-05-06 19:06:54 UTC
This bug is open for a Fedora version that is no longer maintained and
will not be fixed by Fedora. Therefore we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen thus bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

Note You need to log in before you can comment on or make changes to this bug.