file selector hang *for some dozen seconds* if previous save location doesn't exist.



16 years ago
3 years ago


(Reporter: jmarodon, Assigned: law)




Firefox Tracking Flags

(Not tracked)




16 years ago
User-Agent:       Mozilla/5.0 (compatible; Konqueror/3.0.0-10; Linux)
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; fr-FR; rv:1.3.1) Gecko/20030425

From a webmail (, i asked to save an attachement, using  
browser context menu save link target as...  
The previous location i saved a link target was an smb mount which wasn't  
mounted this time. 
i was root  (shame on me ;-) 
didn't tested what it would do on an existing path but with no permissions, 
and with a non-root user. 

Reproducible: Always

Steps to Reproduce: a link target on a mounted network share. close Mozilla  
2.unmount the share Mozilla. save link target as... 
Actual Results:  
file selector freezes, i can move the file selector window, but neither it nor 
the browser window refreshes nor responds to mouse/kb events. 
killall mozilla-bin doesn't help, i have to killall -9 mozilla-bin 

Expected Results:  
the file selector should choose a default location like / or ~, or the upper 
existing part of the previous path 

Redhat 7.3, glibc upgraded to 2.3.2-11.9 
2.4.18-3 - athlon 

Comment 1

16 years ago
Doesn't happen on windows with a deleted folder, so the bug is obviously in 
the file selector dialog. 
Keywords: hang, pp

Comment 2

16 years ago
Found that if i'm patient, within ~40sec it finally points to default ~ dir and
everything goes back to normal.
Must be user-profile related, as creating a new mozilla user profile, it points
back to ~ if we rm -rf previous save location. 
decreased sev from critical to minor, cleared hang flag.
Severity: critical → minor
Keywords: hang
Summary: file selector hang if previous save location doesn't exist. → file selector hang *for some dozen seconds* if previous save location doesn't exist.
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Last Resolved: 14 years ago
Resolution: --- → EXPIRED
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.