JDK-6559586 : This applet site freeze IE
  • Type: Bug
  • Component: deploy
  • Sub-Component: plugin
  • Affected Version: 6
  • Priority: P4
  • Status: Closed
  • Resolution: Duplicate
  • OS: windows_xp
  • CPU: x86
  • Submitted: 2007-05-18
  • Updated: 2010-08-07
  • Resolved: 2008-01-17
Related Reports
Duplicate :  
Description
FULL PRODUCT VERSION :


ADDITIONAL OS VERSION INFORMATION :
Two Fatal Errors:

First Error: the java runtime environment cannot be loaded.
Second error: Several Java Virtual Machines running in the same process caused an error.

Iexplore.exe error, Application Error as third error:
The instruction at "0x2e746e65" referenced memory at "0x2e746e65". The memory could not be "read". Click on OK to terminate the program

A DESCRIPTION OF THE PROBLEM :
Surfing website: http://www.xs4all.nl/~world2cd/weer/Utrecht-weer-history.htm

Plug in Error


Two Fatal Errors:

First Error: the java runtime environment cannot be loaded.
Second error: Several Java Virtual Machines running in the same process caused an error.

Iexplore.exe error, Application Error as third error:
The instruction at "0x2e746e65" referenced memory at "0x2e746e65". The memory could not be "read". Click on OK to terminate the program


REPRODUCIBILITY :
This bug can be reproduced always.
This looks like a multi-JRE support in browser issue, related to our RFE for JDK 7.

Comments
EVALUATION There have historically been many reports of problems running applets when a large -Xmx setting has been specified via the Java Control Panel. Some bugs where this either definitely is the root cause, or may be the root cause, include 6359309, 6433218, 6516270, 6528750, and 6559586. Up until recently, it was not technically feasible to fix this problem in the Java Plug-In due to its in-process architecture. In recent months a new implementation of the Java Plug-In has been developed which changes the execution model of applets. Instead of running the applets in a JVM embedded in the web browser's process, they are now run in a separate JVM process which communicates back to the web browser. The initial checkin of this work done under bug ID 6622332. This new plug-in solves this problem in two ways. First, since the JVM is no longer running in the same process as the web browser, the address space fragmentation problem (which occurs most often in the Internet Explorer browser) does not interfere with the specification of a large -Xmx value via the Java Runtime Parameters in the Java Control Panel. Second, the new Java Plug-In supports specification of JVM command-line arguments, including -Xmx, on a per-applet basis via a new java_arguments parameter in the applet's HTML. This eliminates the need to do any global setting of this or other parameters in the Java Control Panel. The new Java Plug-In is currently available for testing in the early access builds of the "6uN" release, which can be downloaded from https://jdk6.dev.java.net/6uNea.html . See https://jdk6.dev.java.net/testPlugIn.html for instructions on testing the new Java Plug-In specifically. In 6uN build 10, the new Java Plug-In is enabled by default upon installation on the Windows platform; see the testing instructions for installation on the Solaris and Linux platforms. Customer feedback so far indicates that the new Java Plug-In conclusively solves this longstanding problem. For tracking purposes, this bug is being closed as a duplicate of 6622332, which is the "umbrella" bug covering the initial integration of the new Java Plug-In. Note that currently the new plug-in does not change the default heap size for applets, but we believe that this will be far less of an issue now that an individual applet can request a particular heap size. We are open to revisiting this particular issue, in particular in the context of the new plug-in. Please try the new Java Plug-In and file any issues against it under product java, category java_plugin, subcategory plugin2.
2008-01-17

EVALUATION Closing as not reproducible.
2007-08-20

EVALUATION I can't reproduce this on Windows XP SP2 with IE 7 and a pre-release 1.6.0_02 build. No crashes or freezes upon loading. I don't know what the submitter means by "Several Java Virtual Machines running in the same process caused an error". It has never been supported to have multiple HotSpot JVMs instantiated in the same process, and we do not currently launch multiple JVMs to execute multiple applets on a web page. Marking as incomplete. If you can provide a more reproducible test case please do.
2007-05-21