-
Bug
-
Resolution: Cannot Reproduce
-
P3
-
None
-
5.0
-
x86
-
windows_xp
FULL PRODUCT VERSION :
java version "1.5.0_08"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_08-b03)
Java HotSpot(TM) Client VM (build 1.5.0_08-b03, mixed mode, sharing)
ADDITIONAL OS VERSION INFORMATION :
Microsoft Windows XP
A DESCRIPTION OF THE PROBLEM :
This is a duplicate of bug 4848004
This is a very severe bug affecting following plugins for all 1.5.0 versions (up till 1.5.0_08)
From bug 4848004:
"For every call to a java method from javascript a handle is created and never released. This eventually brings down the machine by exahusting memory, bringing the machine on its knees. Entire application starts to malfunction on javascript side. If the java method call is done inside a javascript eventhandler, the calls line up into the stack and blowing the browser into dust. This is a very severe bug, and I am surprised to see a basic handle management was taken bugged down on new plugins."
REPRODUCIBILITY :
This bug can be reproduced always.
---------- BEGIN SOURCE ----------
From bug 4848004:
Open window task manager and observe the number of handles and memory while running the following test case
---------------------------------------------------------------------------
** The following html is used: (test1.htm)
---------------------------------------------------------------------------
<html>
<head>
<script LANGUAGE="JavaScript">
function blowHandles() {
for (var i=0;i<10000;i++) { a1.method1 (); }
window.setInterval(blowMoreHandles,5);
}
function blowMoreHandles() {
a1.method1 ();
}
</script>
</head>
<body>
<input type=button onclick="blowHandles()" value="Test"></input>
<APPLET code="test1.applet1.class" archive="test1.jar" id="a1" name="a1">
<PARAM NAME = "scriptable"VALUE="true">';
</APPLET>
</body>
</html>
---------------------------------------------------------------------------
---------------------------------------------------------------------------
** The following applet: (test1/applet1.java)
---------------------------------------------------------------------------
package test1;
import java.applet.*;
public class applet1 extends Applet {
public void method1 () {}
}
EXPECTED VERSUS ACTUAL BEHAVIOR :
Handles should not increase, and MUST be release after each java metho call from javascript.
Handles are created and never released until the computer goes out of resources.
REPRODUCIBILITY :
This bug can be reproduced always.
---------- BEGIN SOURCE ----------
---------------------------------------------------------------------------
** The following html is used: (test1.htm)
---------------------------------------------------------------------------
<html>
<head>
<script LANGUAGE="JavaScript">
function blowHandles() {
for (var i=0;i<10000;i++) { a1.method1 (); }
window.setInterval(blowMoreHandles,5);
}
function blowMoreHandles() {
a1.method1 ();
}
</script>
</head>
<body>
<input type=button onclick="blowHandles()" value="Test"></input>
<APPLET code="test1.applet1.class" archive="test1.jar" id="a1" name="a1">
<PARAM NAME = "scriptable"VALUE="true">';
</APPLET>
</body>
</html>
---------------------------------------------------------------------------
---------------------------------------------------------------------------
** The following applet: (test1/applet1.java)
---------------------------------------------------------------------------
package test1;
import java.applet.*;
public class applet1 extends Applet {
public void method1 () {}
}
---------- END SOURCE ----------
Release Regression From : 1.4.2
The above release value was the last known release where this
bug was not reproducible. Since then there has been a regression.
java version "1.5.0_08"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_08-b03)
Java HotSpot(TM) Client VM (build 1.5.0_08-b03, mixed mode, sharing)
ADDITIONAL OS VERSION INFORMATION :
Microsoft Windows XP
A DESCRIPTION OF THE PROBLEM :
This is a duplicate of bug 4848004
This is a very severe bug affecting following plugins for all 1.5.0 versions (up till 1.5.0_08)
From bug 4848004:
"For every call to a java method from javascript a handle is created and never released. This eventually brings down the machine by exahusting memory, bringing the machine on its knees. Entire application starts to malfunction on javascript side. If the java method call is done inside a javascript eventhandler, the calls line up into the stack and blowing the browser into dust. This is a very severe bug, and I am surprised to see a basic handle management was taken bugged down on new plugins."
REPRODUCIBILITY :
This bug can be reproduced always.
---------- BEGIN SOURCE ----------
From bug 4848004:
Open window task manager and observe the number of handles and memory while running the following test case
---------------------------------------------------------------------------
** The following html is used: (test1.htm)
---------------------------------------------------------------------------
<html>
<head>
<script LANGUAGE="JavaScript">
function blowHandles() {
for (var i=0;i<10000;i++) { a1.method1 (); }
window.setInterval(blowMoreHandles,5);
}
function blowMoreHandles() {
a1.method1 ();
}
</script>
</head>
<body>
<input type=button onclick="blowHandles()" value="Test"></input>
<APPLET code="test1.applet1.class" archive="test1.jar" id="a1" name="a1">
<PARAM NAME = "scriptable"VALUE="true">';
</APPLET>
</body>
</html>
---------------------------------------------------------------------------
---------------------------------------------------------------------------
** The following applet: (test1/applet1.java)
---------------------------------------------------------------------------
package test1;
import java.applet.*;
public class applet1 extends Applet {
public void method1 () {}
}
EXPECTED VERSUS ACTUAL BEHAVIOR :
Handles should not increase, and MUST be release after each java metho call from javascript.
Handles are created and never released until the computer goes out of resources.
REPRODUCIBILITY :
This bug can be reproduced always.
---------- BEGIN SOURCE ----------
---------------------------------------------------------------------------
** The following html is used: (test1.htm)
---------------------------------------------------------------------------
<html>
<head>
<script LANGUAGE="JavaScript">
function blowHandles() {
for (var i=0;i<10000;i++) { a1.method1 (); }
window.setInterval(blowMoreHandles,5);
}
function blowMoreHandles() {
a1.method1 ();
}
</script>
</head>
<body>
<input type=button onclick="blowHandles()" value="Test"></input>
<APPLET code="test1.applet1.class" archive="test1.jar" id="a1" name="a1">
<PARAM NAME = "scriptable"VALUE="true">';
</APPLET>
</body>
</html>
---------------------------------------------------------------------------
---------------------------------------------------------------------------
** The following applet: (test1/applet1.java)
---------------------------------------------------------------------------
package test1;
import java.applet.*;
public class applet1 extends Applet {
public void method1 () {}
}
---------- END SOURCE ----------
Release Regression From : 1.4.2
The above release value was the last known release where this
bug was not reproducible. Since then there has been a regression.