Closed Bug 264202 Opened 20 years ago Closed 20 years ago

Silverstonetek.com crashes Mozilla

Categories

(SeaMonkey :: General, defect)

x86
Linux
defect
Not set
critical

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: chris, Unassigned)

References

()

Details

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.3) Gecko/20041007 Debian/1.7.3-5
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.3) Gecko/20041007 Debian/1.7.3-5

Going to this web page http://www.silverstonetek.com/products-lc09.htm crashes
both Mozilla and the latest version of Firefox.

Reproducible: Always
Steps to Reproduce:
1. Open up the http://www.silverstonetek.com/products-lc09.htm page.
2.
3.

Actual Results:  
Mozilla crashes.

Expected Results:  
Opened the web page.
I can't reproduce using 1.7.3, 1.7.4 20041012, or trunk 20041013 on WinXPSP2 
using Shockwave Flash 7.0 r19 or SuSe 9.1 1.7.4 20040926 using Shockwave Flash
7.0 r25

What version of Flash are you using?
added URL to summary.
URL is a WFM with Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8a5)
Gecko/20041009

The page contains some flash. Maybe a flash crash?
Summary: Crashes Mozilla → Silverstonetek.com crashes Mozilla
Installing flash version 7 fixed the crash.  Thank you for finding the problem.
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → FIXED
Status: RESOLVED → UNCONFIRMED
Resolution: FIXED → ---
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago20 years ago
Resolution: --- → INVALID
Chris clicking on RESOLUTION above takes you to
https://bugzilla.mozilla.org/bug_status.html

this shows that FIXED isn't the correction resolution, so i'll mark it as WFM
for you...reopening
Status: RESOLVED → UNCONFIRMED
Resolution: INVALID → ---
and wfm'ing it.
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago20 years ago
Resolution: --- → WORKSFORME
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7) Gecko/20040618
Shockwave Flash 7.0 r25
I do not reproduce the bug.
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.