-
Bug
-
Resolution: Fixed
-
P1
-
6u10
Recent changes in 6678929 for startup time optimization have introduced an intermittent failure to bootstrap the new plug-in. The conditions under which it fails are currently unclear. The failure is intermittent but the root cause is clear; an initialization cycle was introduced that needs to be broken. The stack trace is below:
java.lang.UnsatisfiedLinkError: com.sun.deploy.config.WinConfig.getPlatformMaxCommandLineLength()I
at com.sun.deploy.config.WinConfig.getPlatformMaxCommandLineLength(Native Method)
at com.sun.deploy.config.Config.<clinit>(Config.java:721)
at sun.plugin2.util.NativeLibLoader.tryLoadingFromJRE(NativeLibLoader.java:86)
at sun.plugin2.util.NativeLibLoader.load(NativeLibLoader.java:65)
at sun.plugin2.main.client.PluginMain.<clinit>(PluginMain.java:55)
The NativeLibLoader may not touch the Config class.
java.lang.UnsatisfiedLinkError: com.sun.deploy.config.WinConfig.getPlatformMaxCommandLineLength()I
at com.sun.deploy.config.WinConfig.getPlatformMaxCommandLineLength(Native Method)
at com.sun.deploy.config.Config.<clinit>(Config.java:721)
at sun.plugin2.util.NativeLibLoader.tryLoadingFromJRE(NativeLibLoader.java:86)
at sun.plugin2.util.NativeLibLoader.load(NativeLibLoader.java:65)
at sun.plugin2.main.client.PluginMain.<clinit>(PluginMain.java:55)
The NativeLibLoader may not touch the Config class.
- relates to
-
JDK-6678929 Slow client JVM initialization at applet launch time (2)
- Resolved