273761 - Yahoo! games runs into Java error (Poker in this case), then Firefox crashes...just started happening on Monday

Status: RESOLVED EXPIRED

(Firefox :: General, defect)

Description

[Mark]

User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0

Yahoo! games (Poker in my case) fails with some kind of Java error even though
Java is enabled.  When I open the particular 'poker room' in Yahoo!  It says
Java is not enabled, but it is.  Then within seconds, Firefox fails.  This did
not happen ever before Monday.  Now it is also happening if I use Netscape as
well.  Neither happened previously to Monday.

This happens every time and usually forces me to restart my iBook.  Yahoo!s
response was that Games do not work with newer versions of Netscape or any
version of Firefox.  Since I have been using both for months without any issues
at Yahoo! Games, I wonder if they changed something.  They do say I can use an
older version of Netscape, but why?

Reproducible: Always
Steps to Reproduce:
1.  Open Yahoo! Games
2.  Select Hold'em Poker, and a new window opens with the different games available
3.  Before displaying, it gets an error with Java then crashes Firefox

Actual Results:  
Crashes Firefox and usually forces a complete restart of my iBook

Expected Results:  
Open and play

Additionally, Talkback is now refusing to send the error report, the queue just
keeps building up and never is able to send.

If this can not be addressed, I will need to find another browser to work
with...I can not keep having the machine crash.

Comment 1

[Nickolay_Ponomarev]

what is "some kind of Java error"?

Comment 2

[Devin Poolman]

I am also seeing this same problem with Yahoo Bridge on my Mac (10.3.8), and it
works with Safari.  Steps to reproduce:

1. Go to http://games.yahoo.com/games/login2?page=br 
2. Select a room to play in (Social)
3. Applet tries to load in a new window - briefly see
java.lang.InterruptedException message, then Yahoo provided message about not
being supported (turn Java on, etc..)
4. Wait about 10 seconds and Firefox crashes

Can't say whether it used to work or not.

Here is the stack trace I got from the console:

> no proxy
> 
> java.lang.InterruptedException
> 	at java.lang.Object.wait(Native Method)
> 	at java.lang.Thread.join(Thread.java:941)
> 	at java.lang.Thread.join(Thread.java:994)
> 	at sun.applet.AppletPanel.run(AppletPanel.java:323)
> 	at java.lang.Thread.run(Thread.java:491)

Also submitted Trackback TB4574730E.

Comment 3

[Devin Poolman]

Yahoo Bridge works after installing Java Embedding Plugin -
http://javaplugin.sourceforge.net.

Is that expected? If so, not a bug?

Comment 4

[Gervase Markham [:gerv]]

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/

Comment 5

[Gervase Markham [:gerv]]

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.