Bug 620553 - Nautilus is slow when browsing folders with large numbers of items
Summary: Nautilus is slow when browsing folders with large numbers of items
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: nautilus
Version: 13
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Tomáš Bžatek
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-08-02 20:12 UTC by chris bumgarner
Modified: 2015-03-03 22:51 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2011-06-29 12:38:30 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description chris bumgarner 2010-08-02 20:12:50 UTC
Description of problem:
This started within the last week. Nautilus takes way too much time opening folders that contain a large number of items. I timed it when opening /usr/share/doc, it took 1 min 10 seconds. It only has about 900 items in it. And once it is open, it is slow to respond to a double-click. 

While waiting, cpu usage is about 50% the entire time. But there is little to no disk i/o during the wait.

I tried uninstalling extensions, but there is no change in behavior.

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

How reproducible:
100%, but didn't start until recently

Steps to Reproduce:
1. Open Nautilus
2. Browse to any folder with a large number of items, such as /usr/lib/
3. wait for about 60 or more seconds, depending on number of items.
4. Double-click a sub-folder.
5. wait 5 or 6 seconds
  
Actual results:
Takes one minute ten seconds to open /usr/share/doc (956 items). Takes 5 or 6 seconds to open a sub-folder, without giving any immediate feedback as to whether it detected my double-click.

Expected results:
Operate without so much wait. 

Additional info:
Oddly, speed is excellent when browsing with open file dialog boxes (such as gedit).

Comment 1 Bug Zapper 2011-06-01 12:15:14 UTC
This message is a reminder that Fedora 13 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 13.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '13'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 13's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 13 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 2 Bug Zapper 2011-06-29 12:38:30 UTC
Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this 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.