-
Bug
-
Resolution: Cannot Reproduce
-
P4
-
None
-
1.2.2_001
-
x86
-
windows_nt
The memory leak is seen in JDK/plugin 1.2.2_001, 1.2.1_003.
This may also be a duplicate of 4263853, which is fixed in jdk1.2.2_003.
The attached test would show clearly the problem (unzip the zip archive and load the html page) In jdk1.2.2_001/jdk1.2.1_003 he old JavaStatics applet instance would not get finalized upon reloading. OptimizeIt showed the number of instances just keep increasing as many time as the number of reload. Both the solaris and windows version of jdk/plugins showed the same problem.
The same applet, when run on jdk1.2.2_003, showed that finalize() actually was called. OptimizeIt showed that there were 2 at most instances of JavaStatics existed at any time.
The customer have tested on the following for windows:
a. the -classic option of the publicly available 1.3 beta,
b. the shipping 1.2.2 JDK, or
c. the publicly available Swing 1.1.1 on JDK 1.1
I have also tested for jdk1.2.2_001 and jdk 1.2.1_003 for solaris platforms.
This may also be a duplicate of 4263853, which is fixed in jdk1.2.2_003.
The attached test would show clearly the problem (unzip the zip archive and load the html page) In jdk1.2.2_001/jdk1.2.1_003 he old JavaStatics applet instance would not get finalized upon reloading. OptimizeIt showed the number of instances just keep increasing as many time as the number of reload. Both the solaris and windows version of jdk/plugins showed the same problem.
The same applet, when run on jdk1.2.2_003, showed that finalize() actually was called. OptimizeIt showed that there were 2 at most instances of JavaStatics existed at any time.
The customer have tested on the following for windows:
a. the -classic option of the publicly available 1.3 beta,
b. the shipping 1.2.2 JDK, or
c. the publicly available Swing 1.1.1 on JDK 1.1
I have also tested for jdk1.2.2_001 and jdk 1.2.1_003 for solaris platforms.
- relates to
-
JDK-4263853 java plugin 1.2.2 has memory leaks on win95
- Resolved