288928 - Download causes Firefox to freeze and a hard kill is necessary

Status: RESOLVED EXPIRED

(Toolkit :: Downloads API, defect)

Description

[ianhar]

User-Agent:       Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; .NET CLR 1.1.4322; MSN 9.0;MSN 9.1; MSNbQ002; MSNmen-us; MSNcOTH; MPLUS)
Build Identifier: 

Foxfire Download quit working. Foxfire freeze and has to be hard killed.  
Download popup window will not stay open but for about 2 seconds when using
"ctrl J".  I did not know I had to clear the DOWNLOAD MANAGER area.  It was set
to MANUAL CLEAR.  Foxfire freezes when I try to CLEAR DOWNLOAD MANAGER.  Is
there a way to use Windows Explorer to delete the DOWNLOAD HISTORY files.  If I
can get this CLEARed I will set to CLEAR at completion of DOWNLOAD as I don't 
need it.  The DOWNLOAD MANAGER is a real drag on download time.

Reproducible: Always

Steps to Reproduce:
1.Use FOXFIRE to DOWNLOAD file from URL and FOXFIRE will freeze everytime.
2.DOWNLOAD worked fine until today.  I think the capacity was exceeded and 
something broke.
3.

Actual Results:  
Foxfire freezes! ARG! 

Expected Results:  
Foxfire should have downloaded the file from the internet site to a directory 
on my C hard drive.

Comment 1

[Ali Ebrahim]

Fixing summary. I'm going to assume that the reporter meant Firefox.

Comment 2

[Andrea Aime]

Hum... I'm experiencing something similar, but I have an explaination for what's
happening to me.
Some days ago I've downloaded something directly on my notebook share, that is,
on a network path: \\mynotebook\shared\xxx
Now firefox freezes whenever I try to download something and ask it to save it
to disk, presumably because the notebook is not connected. I have to kill
Firefox since there is no way out.
Deleting the last download directory from userPref.js solves the problem.

Comment 3

[Patricia F. Anderson]

I have experienced this problem (Firefox freezing during "Save Page As"
downloads and requiring a hard kill) between 20-30 times in the past 3 months. I
upgraded Firefox to the new version, and it still happens. I am currently using
Firefox 1.0.2 on a Macintosh iBook G4 running OSX version 10.3.9. This tends to
occur when I am doing multiple downloads in rapid succession. It does not matter
if I switch sites from which I am downloading or if they are all from the same
site. I tried only downloading 'page as text' or 'page as HTML' instead of
'complete Web page', but it still happens. It does not happen during normal
browsing, only during downloads of pages. I've been avoiding it but copying text
or source and pasting it into BBEdit, but this is not always an option for my
research needs. What I tend to do is kill the app, restart the computer, and try
to remember where I was when it crashed. I am also going to try increasing the
memory allocation for the application. 

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.