229910 - crash when I right-click->'save link to disk' on the the download link, then click 'save'.

Status: RESOLVED DUPLICATE of bug 228384

(Toolkit :: Downloads API, defect)

Description

[Morten Bojsen-Hansen]

User-Agent:       Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; MyIE2)
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6b) Gecko/20031214 Firebird/0.7+

At http://www.customize.org/details/6695 I have to use the 'save link to disk' 
feature in the right-click menu because the webmaster has forgotten to set the 
mime-type to wsz (winamp skin format). The problem is that when I do so, as 
soon as I have chosen a proper location/name for the file and hit 'save', 
Firebird crashes. Actually after some testing it happens _everytime_ I use 
the 'Save link to Disk' feature - I just tried saving a couple of random pages, 
both on my brother's and on my own PC - Firebird crashed each and every time.
Note: My brother's setup is Windows 98 w/ Firebird build (zip) from 16. 
December.

Reproducible: Always

Steps to Reproduce:
1. Go to http://www.customize.org/details/6695
2. Right click the 'Download' link at the top-right of the page and 
choose 'Save link to Disk'
3. When you are prompted to save the file, hit 'Save'.
4. Firebird should now crash.
Actual Results:  
... uhm, Firebird crashed (ie: closed down with an error).

Expected Results:  
It should of course have downloaded the file, without any problems.

I tried both on my brother's PC (win98 w/ default theme) and on my own (win2k 
w/ breeze theme) and both crash. It was a little different on my brother's PC 
though. His crashed instantly, meaning as soon as I chose 'Save link to Disk' 
and before the prompt.

Comment 1

[José Jeria]

This has been fixed, please download a newer build. If you can reproduce with a
brand new build, please reopen.

*** This bug has been marked as a duplicate of 228384 ***

Comment 2

[Morten Bojsen-Hansen]

Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6b) Gecko/20040102
Firebird/0.7+

With this newer build, the bug is gone. Thank you. :)