Closed Bug 196654 Opened 22 years ago Closed 22 years ago

Phoenix crashes/hangs when clicking on a file to download

Categories

(Toolkit :: Downloads API, defect)

x86
Windows XP
defect
Not set
critical

Tracking

()

VERIFIED DUPLICATE of bug 195386

People

(Reporter: dtsweb, Assigned: bugzilla)

References

()

Details

(Keywords: crash)

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3b) Gecko/20030228 Phoenix/0.5
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3b) Gecko/20030228 Phoenix/0.5

Going to http://komodo.mozilla.org/pub/phoenix/nightly/latest-trunk/ and
clicking on phoenix-win32.zip crashes Phoenix with the message: 'The instruction
at "0x1001085b" referenced memory at "0x00000000". The memory could not be "read".'

Downloading from FTP servers seems to cause problems too. When clicking on an
ftp:// link Phoenix often hangs network wise (switching tabs and scrolling
through pages still works but anything that requires transferring data over the
Network gets stuck). I'll try to find an example of this.

Reproducible: Always

Steps to Reproduce:
1. Go to http://komodo.mozilla.org/pub/phoenix/nightly/latest-trunk/
2. Click on phoenix-win32.zip

Actual Results:  
Phoenix crashes.

Expected Results:  
Ask where to save the file and download it.
Here's an FTP example that also crashes Phoenix:

http://h18007.www1.hp.com/support/files/evonotebook/us/download/17408.html

Note: Whether Phoenix crashes completely or hangs as described seems to be
dependant on the OSs condition (the first time today it just hung, now it always
abends and I haven't restarted in between).
This sounds like bug #195386 - hence I'll resolve this one as duplicate! Please
try again with a newer build. If problem still exists, please feel free to
reopen this bug!

*** This bug has been marked as a duplicate of 195386 ***
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Keywords: crash
Resolution: --- → DUPLICATE
v
Status: RESOLVED → VERIFIED
Product: Firefox → Toolkit
You need to log in before you can comment on or make changes to this bug.