[Bug 15480] New: (breezy 4) 100% cpu by nautilus while displaying large folders

bugzilla-daemon at bugzilla.ubuntu.com bugzilla-daemon at bugzilla.ubuntu.com
Thu Sep 15 10:17:35 UTC 2005


Please do not reply to this email.  You can add comments at
http://bugzilla.ubuntu.com/show_bug.cgi?id=15480
Ubuntu | nautilus

           Summary: (breezy 4) 100% cpu by nautilus while displaying large
                    folders
           Product: Ubuntu
           Version: unspecified
          Platform: i386
        OS/Version: other
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: nautilus
        AssignedTo: seb128 at ubuntu.com
        ReportedBy: ubuntubugz at poptones.f2o.org
         QAContact: desktop-bugs at lists.ubuntu.com


While using a spatial view of a folder, opening a folder containing a large
number of images (as few as a hundred to several thousand) results in nautilus
using 100% of the cpu as the thumbnails are rendered. The program will become
intermittently responsive as the content is updated until all thumbnails are
drawn. The folder may then be scrolled normally, programs activated from
clicking on objects, etc. However, nautilus will AGAIN jump to 100% cpu
utilization - again and again, so long as the spatial views of these large
folders are drawn onscreen.

I installed the debugging symbols but when I try the instructions on bug#10320
nautilus never opens under the debugger. it eventually starts back up, but not
under gdb - so no trace, no stack.

When viewing an encrypted space, during each of these lockups kcrypt occupies
2-6% of cpu time *exactly* as happens when the folder is first opened -
indicating nautilus seems to be refreshing its view of every file in these
displayed folders (perhaps due to some spurious trigger that their contents may
have changed?)

-- 
Configure bugmail: http://bugzilla.ubuntu.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.




More information about the desktop-bugs mailing list