This page hangs when run

RESOLVED WORKSFORME

Status

RESOLVED WORKSFORME
17 years ago
14 years ago

People

(Reporter: neil, Assigned: asa)

Tracking

Trunk
x86
Windows 2000

Firefox Tracking Flags

(Not tracked)

Details

(URL)

(Reporter)

Description

17 years ago
Up until recently I was able to play http://www.globalserve.net/~brent/tech/beam
just fine in mozilla (Slow, but it ran).  I thought the problem was The
JavaScript Strict warnings, but I turned those off and it still won't run.

Unfortunatly the source is hard to read (5k web page competition).  It uses
serTimeout to animate which has caused the debugger to lockup in the past on my
350MHz machine.

Build 2002032803
(Reporter)

Comment 1

17 years ago
I did manage to get it to run, but as soon as I open another browser window, it
locks up again.  Does anyone else see this?

Comment 3

17 years ago
WorksForMe on linux 2002032808 with a AMD 1700+ CPU. Probably a performance issue.

Comment 4

17 years ago
worksforme with Linux build 20020328 on a PII-450.  Are you running with the
debugger active?
(Reporter)

Comment 5

17 years ago
Nope.  I have 2 browser windows open (One of them on mozillazine.org and the 
other on the game).  The game just hits 99% processor usage and stops painting.
Strict mode is also off and the console isn't open.
wfm with win2k build 20020404 and an Athlon1.2Ghz

Comment 7

17 years ago
The URL doesn't exist anymore so we need either a
copy  (or even better) testcase or a new URL.
If nothing shows up this bug can be closed.
(Reporter)

Comment 8

17 years ago
I know, my ISP deleted it :|
I have no way to get it back.

Comment 9

17 years ago
As the bug cannot be duplicated (because the page was deleted), this is invalid,
and should be marked as such.

(If the reporter can attach the problem file(s), this could be reopened.)

Comment 10

17 years ago
marking worksforme.  reopen if you can provide a testcase.
Status: NEW → RESOLVED
Last Resolved: 17 years ago
Resolution: --- → WORKSFORME
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.