FULL PRODUCT VERSION :
java version "1.6.0_21"
Java(TM) SE Runtime Environment (build 1.6.0_21-b06)
Java HotSpot(TM) Client VM (build 17.0-b16, mixed mode, sharing)
ADDITIONAL OS VERSION INFORMATION :
Microsoft Windows XP [Version 5.1.2600]
A DESCRIPTION OF THE PROBLEM :
Regression: With Java 1.6.0_21, the ("\\StringFileInfo\\%04x%04x\\CompanyName") has changed in the java.exe and javaw.exe programs from "Sun Microsystems, Inc" to "Oracle".
This causes a severe regression for programs that need to identify the Sun/Oracle HostSpot VM such that they know whether the "-XX:MaxPermSize" argument needs to be used or not.
Any Eclipse version since 3.3 (released 2007) until and including the recent Helios release (2010) has been reported to crash with an OutOfMemoryError due to this regression, as per http://wiki.eclipse.org/FAQ_How_do_I_run_Eclipse%3F and https://bugs.eclipse.org/bugs/show_bug.cgi?id=319514 . The OutOfMemoryError is not understandable for end users, and the workaround is not obvious.
This is especially severe since Java 1.6u21 is deployed to end users through automatic update, such that working applications start failing due to the update; and, the change has been in troduced without upfront warning. Moreover, the very same JVM still identifies itself as "
java.vendor=Sun Microsystems Inc.
in the System Properties, so the particular change of version string to Oracle is not understandable and a fix restoring original behavior is requested.
STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
1. Select the java.exe or javaw.exe program
2. Right-click > Properties, pick the "Version" tab
--> with Java 1.6.0_21, the "Company" String has been changed
from "Sun Microsystems, Inc" to "Oracle"
EXPECTED VERSUS ACTUAL BEHAVIOR :
The "Company " String should remain as in previous releases, "Sun Microsystems, Inc"
The "Company" String has been changed to "Oracle"
This bug can be reproduced always.
CUSTOMER SUBMITTED WORKAROUND :
Avoid upgrading to 1.6.0_21.
Or, Manually configure any affected Java Program to launch with proper VM arguments. See also https://bugs.eclipse.org/bugs/show_bug.cgi?id=319514#c22