P3
Snv b34, vermillion b06, jdk1.5.0_06-04
reproduce steps:
1. start firefox
2. load an applet (e.g. http://quarterfinal.prc/demoapplet/testcase/NewApplet.html). This applet can not be loaded successfully, the class file is missing.
3. right click the mouse on the applet area to open the Java Console
4. monitor the cpu usage of the firefox process by prstat, the cpu usage increaces dramatically. and the browser hangs.
Sometimes this bug can be reproduced after repeating these steps 2 or 3 times.
-- New report from another customer ...
FULL PRODUCT VERSION :
java version "1.6.0-beta2"
Java(TM) SE Runtime Environment (build 1.6.0-beta2-b84)
Java HotSpot(TM) Client VM (build 1.6.0-beta2-b84, mixed mode, sharing)
Java Plug-in 1.6.0-beta2
Using JRE version 1.6.0-beta2 Java HotSpot(TM) Client VM
ADDITIONAL OS VERSION INFORMATION :
Windown XP SP2 (Czech)
A DESCRIPTION OF THE PROBLEM :
After Applet throws an exception (error), it gets reported nicely in a popup window, but then Firefox hangs forever.
Tested with Firefox 1.5.0.4 and Mustang b84 (it did that in earlier builds too).
STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
Make an applet throw an exception - be it simple missing class file for the Applet, or a RuntimeException thrown in a Thread started by the Applet, whatever.
Here is the simplest test case for the problem - a missing applet class:
--------- crash1.html -------------------------------------------
<html>
<body>
<applet code="nonexisting.class" width=1 height=1>
</applet>
</body>
</html>
EXPECTED VERSUS ACTUAL BEHAVIOR :
EXPECTED -
Firefox should recover nicely, possibly not showing the failing applet.
Internet Explorer, for example, generates a "java.lang.ClassNotFoundException: nonexisting.class" and then returns control to the user.
ACTUAL -
Firefox will hang badly. Will not refresh, you can still close the browser window but the process will still hang in the memory, preventing you from starting a new browser. You have to kill firefox.exe from the task manager.
REPRODUCIBILITY :
This bug can be reproduced always.
Turns out this is (probably) a Gecko bug. See
http://bugzilla.mozdev.org/show_bug.cgi?id=16670 for more information.
it can be reproduced under FireFox 2.0.0.3 (which is the latest) but it's
gone in FireFox 3.0 alpha 2. One would hope they fold in this fix into
FireFox 2.x in the near future.
reproduce steps:
1. start firefox
2. load an applet (e.g. http://quarterfinal.prc/demoapplet/testcase/NewApplet.html). This applet can not be loaded successfully, the class file is missing.
3. right click the mouse on the applet area to open the Java Console
4. monitor the cpu usage of the firefox process by prstat, the cpu usage increaces dramatically. and the browser hangs.
Sometimes this bug can be reproduced after repeating these steps 2 or 3 times.
-- New report from another customer ...
FULL PRODUCT VERSION :
java version "1.6.0-beta2"
Java(TM) SE Runtime Environment (build 1.6.0-beta2-b84)
Java HotSpot(TM) Client VM (build 1.6.0-beta2-b84, mixed mode, sharing)
Java Plug-in 1.6.0-beta2
Using JRE version 1.6.0-beta2 Java HotSpot(TM) Client VM
ADDITIONAL OS VERSION INFORMATION :
Windown XP SP2 (Czech)
A DESCRIPTION OF THE PROBLEM :
After Applet throws an exception (error), it gets reported nicely in a popup window, but then Firefox hangs forever.
Tested with Firefox 1.5.0.4 and Mustang b84 (it did that in earlier builds too).
STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
Make an applet throw an exception - be it simple missing class file for the Applet, or a RuntimeException thrown in a Thread started by the Applet, whatever.
Here is the simplest test case for the problem - a missing applet class:
--------- crash1.html -------------------------------------------
<html>
<body>
<applet code="nonexisting.class" width=1 height=1>
</applet>
</body>
</html>
EXPECTED VERSUS ACTUAL BEHAVIOR :
EXPECTED -
Firefox should recover nicely, possibly not showing the failing applet.
Internet Explorer, for example, generates a "java.lang.ClassNotFoundException: nonexisting.class" and then returns control to the user.
ACTUAL -
Firefox will hang badly. Will not refresh, you can still close the browser window but the process will still hang in the memory, preventing you from starting a new browser. You have to kill firefox.exe from the task manager.
REPRODUCIBILITY :
This bug can be reproduced always.
Turns out this is (probably) a Gecko bug. See
http://bugzilla.mozdev.org/show_bug.cgi?id=16670 for more information.
it can be reproduced under FireFox 2.0.0.3 (which is the latest) but it's
gone in FireFox 3.0 alpha 2. One would hope they fold in this fix into
FireFox 2.x in the near future.