-
Bug
-
Resolution: Fixed
-
P3
-
6u10
-
b21
-
generic
-
generic
-
Verified
The user experience of the applet launch time shall be at least very close to the performance of the legacy plugin.
A new client JVM is launched in case that no suitable JVM is running,
which would satisfy the to be launched applet.
Launching and initializing a new client JVM currently takes about 2 seconds,
which is not acceptable and above the legacy startup time.
A new client JVM is launched in case that no suitable JVM is running,
which would satisfy the to be launched applet.
Launching and initializing a new client JVM currently takes about 2 seconds,
which is not acceptable and above the legacy startup time.
- relates to
-
JDK-6678929 Slow client JVM initialization at applet launch time (2)
-
- Resolved
-
-
JDK-6697433 b23- java console content isn't initially well formatted with OOPP
-
- Resolved
-
-
JDK-6675834 (Nightly) : Some of the Liveconnect scenarios are making browser to hang when run with new Plug-in
-
- Closed
-
-
JDK-6714877 plugin2 printing is not working - CNFE sun/plugin2/main/client/WPluginEmbeddedFrame
-
- Closed
-