Closed Bug 318948 Opened 19 years ago Closed 19 years ago

the 1st time the "save as" dialog appears in a session it takes 100% of cpu and memory

Categories

(Toolkit :: Downloads API, defect)

x86
Linux
defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 305970

People

(Reporter: urifrid, Unassigned)

References

()

Details

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8) Gecko/20051111 Firefox/1.5
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8) Gecko/20051111 Firefox/1.5

upon starting the browser, the 1st time in the session that i am trying to download a file, the save as dialog will appear (with the gnome interface) and it will stay "thinking" for up to 30 secs taking with it 100% of cpu and memory as well. while "thinking" the browser will not respond.
this doesn;'t happens the 2nd time the dialog is displayed on the same session. 

Reproducible: Always

Steps to Reproduce:
1.open the browser
2.download a file
3.the "save as" dialog will be displayed and it'll take 100% of cpu and memory for up to 30secs during which the browser doesn't respond

Actual Results:  
the "save as" dialog will be displayed and it'll take 100% of cpu and memory for up to 30secs during which the browser doesn't respond


Expected Results:  
to allow me to chose where to save the file

from what i could determine this is due to the gnome interface (which i still don't understand why you change the save dialog to this), i think it's trying to read every file in the current directory.
Looks like this one: Bug 305970.
Maybe you could try a trunk build?
it looks similar but the results are different.
This was fixed on trunk, but has not been checked into branch (1.5) yet. You can verify this is fixed for yourself by downloading a build from here: http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/latest-trunk/

*** This bug has been marked as a duplicate of 305970 ***
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → DUPLICATE
Product: Firefox → Toolkit
You need to log in before you can comment on or make changes to this bug.