261803 - Browser freeze if javascript calls an applet, which in turn calls another javascript ..

Status: RESOLVED FIXED

(Core Graveyard :: Java: Live Connect, defect)

Description

[Alex Li]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; rv:1.7.3) Gecko/20040913 Firefox/0.10
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; rv:1.7.3) Gecko/20040913 Firefox/0.10

This happens in various versions of Mozilla and Netscape browsers on Windows:
When a javascript calls an applet method, and inside this applet method, another
javascript is called, then the browser will freeze. You may close the browser
window, however, the process in the background must be killed with Task Manager.
Did not test Mozilla on other OS.

Reproducible: Always
Steps to Reproduce:
1. Make a simple java applet, with a method that calls a javascript method, for
example, a simple window.open(); 
2. Make a javascript that will call this java applet method;
3. Make a simple html page and include both the javascript and java applet on
the same page. Create a button to invoke the javascript
4. Open the page with Firefox PR1.0, test by clicking the button within the page.
Actual Results:  
Browser will freeze with no new window opened.

Expected Results:  
It should open a new window. In IE, this behaves normally.

Firefox will allow you to close the window. However, the firefox process remains
in the process list. Need to kill the firefox process with Task Manager before
starting another firefox instance.

Comment 1

[Alex Li]

Test applet uses netscape.javascript.JSObject instead of the 
sun.plugin.javascript.navig5.JSObject. Sun Java Plugin version is 1.4.2_05. 
Tested on both Firefox 1.0PR and IE6.0. IE behaves normally. Firefox freezes.

Comment 2

[Boris Zbarsky [:bzbarsky]]

Alex, is  this a problem with a current trunk build?

Comment 3

[Alex Li]

(In reply to comment #2)
> Alex, is  this a problem with a current trunk build?

I believe so. I tried with release 0.10 and a nightly build 0.9. The same 
problem exist in both.

Comment 4

[Alex Li]

This bug is completely resolved with the latest Java Plugin contained in Sun's 
SDK/JRE 5.0 (Tiger). Just tested with Firefox and Plugin 1.5.0, it works like 
a charm!

Comment 5

[Worcester12345]

Is this a "FIX" or a "WORKSFORME", since it wasn't a mozilla fix, but a Sun one?

Comment 6

[Alex Li]

(In reply to comment #5)
> Is this a "FIX" or a "WORKSFORME", since it wasn't a mozilla fix, but a Sun 
one?

I guess the original problem was a SUN plugin problem. It probably wasn't 
thread-safe with liveconnect. Now, since it works without modifying Mozilla, 
it's a "FIX" for me.

Interestingly though, IE didn't have the same problem even with the same old 
Java Plugin! IE is more robust with plugins?