User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:184.108.40.206) Gecko/20080404 Firefox/220.127.116.11 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:18.104.22.168) Gecko/20080404 Firefox/22.214.171.124 if something is saved to a network path (\\10.0.0.1\...) using "save as" and then that path is unavailable (you move a laptop to another network) attempting to save something else causes a long hang (>min, might be inf). Something like this also happens with "open file" but is resolves it self after a few minutes. editing prefs.js fixes the problem: -user_pref("browser.download.lastDir", "\\\\10.0.0.1\\...."); +user_pref("browser.download.lastDir", "c:\\"); Reproducible: Always Steps to Reproduce: 1. save to a network path 2. make that path unavailable (switch to another network / unplug a cable / etc.) 3. try to save something else Actual Results: hard hang. Expected Results: "save as" dialog box
That sounds like windows standard behavior, it's searching for the drive over the network which doesn't exist.
Ok, this may be a problem in Windows, but it's bad enough that I think it could use a workaround of some kind. Something like; if the current default dir is a network path, spawn a thread to test for the dir, if it doesn't return in X time (~10s) switch the default dir to something sane and use it. (I have no clue how hard this would be so take it with a big grain of salt)
Certainly possible. Currently we just launch the native windows file picker and hand it the path, windows does the rest.
Windows standard behavior eventually comes back with a 'network not available' pop up or similar. Firefox hangs indefinitely. I agree it is pretty annoying and does need fixing.
This bug was reported on Firefox 2.x or older, which is no longer supported and will not be receiving any more updates. I strongly suggest that you update to Firefox 3.6.3 or later, update your plugins (flash, adobe, etc.), and retest in a new profile. If you still see the issue with the updated Firefox, please post here. Also, give a stacktrace. Otherwise, please close as RESOLVED > WORKSFORME http://www.mozilla.com http://support.mozilla.com/kb/Managing+profiles http://support.mozilla.com/kb/Safe+mode https://developer.mozilla.org/En/How_to_get_a_stacktrace_for_a_bug_report
No reply, INCOMPLETE. Please retest with Firefox 3.6.x or later and a new profile (http://support.mozilla.com/kb/Managing+profiles). If you continue to see this issue with the newest firefox and a new profile, then please comment on this bug.