279317 - Downloaded Firefox 1.0 Setup.exe locks up Windows Explorer

Status: RESOLVED EXPIRED

(Firefox :: General, defect)

Description

[Ken D.]

User-Agent:       Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0)
Build Identifier: 

This is strange. I downloaded Firefox 1.0 Setup, which went fine. I am running 
Windows 2000 SP4, browsing with IE 6.0. All MS current security updates have 
been applied. Using Norton Antivirus. 

However, when trying to view and execute the downloaded .exe file, Windows 
Explorer hangs up, with no activity, no response. This is true even when just 
VIEWING the folder to which Firefox was downloaded, let alone trying to execute 
it. 

Task Manager reports Windows Explorer as "not responding." I waited as much as 
10 minutes, but nothing. I deleted the entire folder and downloaded Firefox 
again. Same problem. I did this 3 or 4 times with the same results. 

Other than this download folder, Windows Explorer seems to work fine. The 
download folder is the only one I have found that gives me this problem. 

The download folder is on a network drive (my LAN). So, I tried downloading the 
file to a local drive and did NOT have the problem. 

For some reason, when downloaded to a network drive, the file causes Windows 
Explorer either to take an awfully long time just to display its existence or 
to hang completely. 



Reproducible: Always

Steps to Reproduce:
1. Download Firefox 1.0 Setup to a folder on a network drive. 
2. Open Windows Explorer. 
3. Select the download folder. 
 

Actual Results:  
4. Windows Explorer hangs, "not responding." I am unable to view the folder 
contents, select or execute the downloaded file.

Comment 1

[Ken D.]

Update: I am using Firefox 1.0 to add this comment to the bug report. Once
downloaded to a local (not network) drive, the installation went smoothly. 

And kudos to developers! I intended to install Firefox as a trial, figuring that
I would have to start over with Web bookmarks, passwords, and such. That the
installation automatically (with my permission) converted my IE info is
fantastic!! In all likelihood, Firefox will become my default and perhaps only
browser. Thanks, Mozilla. 

One final note on the original bug report. If I were you, I would still treat it
as an problem needing solution, even though there is a work-around. Speaking as
a user, seeing my download cause a lock-up gave me visions of works and viruses
eating their way through my computer. I don't have the fastest computer in the
world, but ten minutes should be enough to display a list of files in a folder,
even a network folder. 

Comment 2

[Nickolay_Ponomarev]

I take it as the report has nothing to do with Firefox's donwload manager. You
downloaded the file and tried to view it with Explorer, right?

Comment 3

[Ken D.]

(In reply to comment #2)
> I take it as the report has nothing to do with Firefox's donwload manager. You
> downloaded the file and tried to view it with Explorer, right?

(In reply to comment #2)
> I take it as the report has nothing to do with Firefox's donwload manager. You
> downloaded the file and tried to view it with Explorer, right?

(In reply to comment #2)
> I take it as the report has nothing to do with Firefox's donwload manager. You
> downloaded the file and tried to view it with Explorer, right?


Right, I think. At the time of the initial report, Download Manager seemed the 
closest fit. 

Still, though not DM's problem, there is something strange and unique about the 
Firefox setup file that makes Windows Explorer get brainlock. Everything, even 
just selecting the file or displaying Properties, even on a local drive, is 
much slower than normal. When the downloaded file is on a network drive, 
whether copied from a local drive or downloaded there directly, it is REALLY, 
REALLY SLOW. Other downloaded files, even bigger ones, do not cause such delays 
in WE. 

Comment 4

[Gervase Markham [:gerv]]

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:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 5

[Gervase Markham [:gerv]]

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.