Closed Bug 361302 Opened 19 years ago Closed 19 years ago

Open and Save dialogs render extremely slowly

Categories

(Firefox :: Shell Integration, defect)

x86
Windows 2000
defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 111821

People

(Reporter: public, Unassigned)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-GB; rv:1.8.1) Gecko/20061010 Firefox/2.0 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-GB; rv:1.8.1) Gecko/20061010 Firefox/2.0 When opening an Open or Save (As) dialog box in Firefox, the window contents render extremely slowly on a PII 333 MHz PC -- something like four seconds to draw in an Open/Save dialog box with about 80 or so items. Controls like the filename box, file type pop-up, main buttons and size grip don't draw until this is complete, leaving gaping holes right through the window. The behaviour is suggestive of a low thread priority being set for the thread owning the window, but Process Explorer shows that Firefox is chewing up the CPU: 100% CPU usage for several seconds with very heavy kernel usage, and the owning thread of the CPU use is firefox.exe, not any OS component. Opening an Open or Save dialog in another app uses no excessive CPU time, although indications go that the app's core thread, not SHLWAPI, own the CPU time for redrawing a common dialog, so this seems consistent. Reproducible: Always Steps to Reproduce: 1. File > Save Page As 2. If the Save dialog shows few or no file, from Save as type, select All files 3. Count the seconds go by, or watch the CPU hit as the window is slowly rendered. Actual Results: Very slow! Expected Results: Such dialog boxes should be instantaneous on all computers no matter how old.
Sounds like a dupe of Bug 111821.
Wonderful, Ria, you're a star. I had realised that it was an extension problem, but read your mail before going through them one by one. I only installed Firefox 2.0 today and this was the first time in ages that I'd installed Talkback ... D'oh. Banished it. *** This bug has been marked as a duplicate of 111821 ***
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.