JDK-6579181 : Java Runtime Environment cannot be loaded
  • Type: Bug
  • Component: deploy
  • Sub-Component: plugin
  • Affected Version: 6
  • Priority: P4
  • Status: Closed
  • Resolution: Duplicate
  • OS: windows_xp
  • CPU: x86
  • Submitted: 2007-07-11
  • Updated: 2011-02-16
  • Resolved: 2007-08-29
Related Reports
Duplicate :  
Description
FULL PRODUCT VERSION :
java version "1.6.0"
Java(TM) SE Runtime Environment (build 1.6.0-b105)
Java HotSpot(TM) Client VM (build 1.6.0-b105, mixed mode, sharing)
1.6.0_02

ADDITIONAL OS VERSION INFORMATION :
Operating System:
	Microsoft Windows XP Professional
	Version: 2002
	Service Pack 2

EXTRA RELEVANT SYSTEM CONFIGURATION :
RAM on client machine: 1 GB
Browser version: Microsoft Explorer Version 6.0, SP2
Java Applet Runtime setting:  -Xms200m -Xmx200m -XX:NewSize=48M -XX:MaxNewSize=48M -XX:SurvivorRatio=4 -XX:PermSize=40m -XX:MaxPermSize=40m

A DESCRIPTION OF THE PROBLEM :
1.Install JRE 1.6 (plugin) in the client machine. Open internet explorer. Open the page http://www.egain.com.
2.Using the same instance of the browser, access the URL http://java.sun.com/applets/jdk/1.4/demo/applets/ArcTest/example1.html
3.The error message "Java Runtime Environment cannot be loaded", with the window title "Java(TM) Plug-in Fatal Error" is displayed.
4.Refresh the page. You get the error message "Several Java Virtual Machines running in the same process caused an error".
5.Once we close the browser, we get the error message 'The instruction at "<some_address>" referenced memory at "<some_address>". The memory could not be "read". Click on OK to terminate the program'.

Note:
1. This issue can be recreated on some machines consistently. It is not consistently reproducible on all client machines.


STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
1.Install JRE 1.6 (plugin) in the client machine. Open internet explorer. Open the page http://www.egain.com.
2.Using the same instance of the browser, access the URL http://java.sun.com/applets/jdk/1.4/demo/applets/ArcTest/example1.html
3.The error message "Java Runtime Environment cannot be loaded", with the window title "Java(TM) Plug-in Fatal Error" is displayed.
4.Refresh the page. You get the error message "Several Java Virtual Machines running in the same process caused an error".
5.Once we close the browser, we get the error message 'The instruction at "<some_address>" referenced memory at "<some_address>". The memory could not be "read". Click on OK to terminate the program'.

Note:
1. This issue can be recreated on some machines consistently. It is not consistently reproducible on all client machines.


EXPECTED VERSUS ACTUAL BEHAVIOR :
EXPECTED -
The applet should have loaded properly, displaying proper data.
ACTUAL -
We get an error message "Java Runtime Environment cannot be loaded", with the window title "Java(TM) Plug-in Fatal Error"

ERROR MESSAGES/STACK TRACES THAT OCCUR :
Java Runtime Environment cannot be loaded

REPRODUCIBILITY :
This bug can be reproduced always.

CUSTOMER SUBMITTED WORKAROUND :
1. Change the Java applet runtime setting to
-Xms150m -Xmx150m -XX:NewSize=48M -XX:MaxNewSize=48M -XX:SurvivorRatio=4
-XX:PermSize=40m -XX:MaxPermSize=40m

2. Access the URL http://java.sun.com/applets/jdk/1.4/demo/applets/ArcTest/example1.html before accessing any other pages from a new instance of the browser.

Comments
EVALUATION 2.Using the same instance of the browser, access the URL http://java.sun.com/applets/jdk/1.4/demo/applets/ArcTest/example1.html 3.The error message "Java Runtime Environment cannot be loaded", with the window title "Java(TM) Plug-in Fatal Error" is displayed. ---This indicates the jvm.dll is loaded but cannot create java heap 4.Refresh the page. You get the error message "Several Java Virtual Machines running in the same process caused an error". ---At this step, since the jvm.dll is loaded by the last step. Plugin mistakenly thinks it is required to load more than one jvm.dll. The error message is misleading. The bottom of the problem is that in the browser process, the usable memory address for java heap is fragmented and there is no CONTIGUOUS area to satisfy minimal heap requirement. I have a tool to walk the process address space. It's useful to tell what is the largest available contiguous address. Please let me know if they want to try it to verify the root cause.
13-07-2007

WORK AROUND remove unused add-ons to the browser. try to use a freshly started browser as possible
13-07-2007