-
Enhancement
-
Resolution: Fixed
-
P4
-
1.4.0
-
hopper
-
x86
-
windows_nt
Problem:
The exact Applet lifecycle sequence is historically differently in JPI on each platforms. This causes a lot of problems in the past because of this consistency, so applet code may work on one platform but completely broken on the other.
Solution:
Revisit the applet lifecycle sequence in JPI and ensure they are consistent across platforms. Also, pay special attention to the applet shutdown sequence to avoid any potential resource leak.
###@###.### 2001-11-05
The exact Applet lifecycle sequence is historically differently in JPI on each platforms. This causes a lot of problems in the past because of this consistency, so applet code may work on one platform but completely broken on the other.
Solution:
Revisit the applet lifecycle sequence in JPI and ensure they are consistent across platforms. Also, pay special attention to the applet shutdown sequence to avoid any potential resource leak.
###@###.### 2001-11-05
- relates to
-
JDK-4672707 Applet lifecycle shutdown sequences causes IE browser hang on page switch:PIT09
- Closed