Closed Bug 258912 Opened 21 years ago Closed 20 years ago

Java Applet Implementation Crashes in Yahoo Games (Specifically Backgammon)

Categories

(Core Graveyard :: Java APIs for DOM, defect)

x86
Windows XP
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED EXPIRED

People

(Reporter: johnk6, Assigned: ashuk)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7) Gecko/20040803 Firefox/0.9.3 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7) Gecko/20040803 Firefox/0.9.3 This has happened three times today and has never happened with IE. And by the way--I lost a game because of it Grrrrr. You'll have to play for a while but then the applet will just lock up. After a couple of minutes the applet vanishes. Sorry, but that's all I have for you. URL to play the games is http://games.yahoo.com Reproducible: Sometimes Steps to Reproduce: 1.Above 2. 3. Actual Results: Above Expected Results: Not locked up--continue play.
I have the same problem on multiple machines, running varous flavors of Java (1.4.x or 1.5) on WinXP and Win2K. Backgammon crashes every single time I exit it. Other games will crash sometimes, too, but backgammon seems to be the worst. I'm using Firefox 1.0. Haven't ever had a problem in Mozilla 1.x or Netscape 7.x (not to mention IE).
Also happens on Firefox 1.0 and 1.0.1, I get this same problem very often at Yahoo Chess. The games will load and work well, but after a while the whole browser, including any tabs and however many different windows of it may be open, will crash. With version 1.0 I used to get a question on whether I want to send a error report to Microsoft, with version 1.0.1 the browser and its windows will just quietly cease to be there and vanish. If you need any help in testing if this bug will vanish with a test version I will be happy to help out, because I like to play a game of chess in the evening. :-)
It also happens with Firefox 1.0.2 in Windows 2000 and is not restricted to Yahoo Games.
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/
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.
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → EXPIRED
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.