-
Bug
-
Resolution: Fixed
-
P3
-
8, 9
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8304789 | 8 | Ivan Bereziuk | P3 | Closed | Cannot Reproduce |
FULL PRODUCT VERSION :
java version "1.8.0_60"
Java(TM) SE Runtime Environment (build 1.8.0_60-b27)
Java HotSpot(TM) Client VM (build 25.60-b23, mixed mode, sharing)
ADDITIONAL OS VERSION INFORMATION :
Microsoft Windows [version 10.0.10240]
A DESCRIPTION OF THE PROBLEM :
Java 7 launchers report too large -Xmx as an error while Java 8 does not. We are using the 32 bit versions.
Here are the different scenarios:
jdk1.7.0_04\bin>java -Xmx2000m
-> error message in console:
Error occurred during initialization of VM
Could not reserve enough space for object heap
Error: Could not create the Java Virtual Machine.
Error: A fatal exception has occurred. Program will exit.
jdk1.7.0_04\bin>javaw -Xmx2000m
-> error message in dialog:
Error: Could not create the Java Virtual Machine.
Error: A fatal exception has occurred. Program will exit.
jdk1.8.0_60\bin>java -Xmx2000m
-> error message in console:
Error occurred during initialization of VM
Could not reserve enough space for 2048000KB object heap
jdk1.8.0_60\bin>javaw -Xmx2000m
-> no error message!
This is very problematic because application shortcuts do contain -Xmx which may have to be adjusted with Java 8 (value that was working with Java 7 does not work with Java 8), but when the user clicks, nothing happens and they have no clue why. Before, there was an error dialog for such problems.
REGRESSION. Last worked in version 7u75
ADDITIONAL REGRESSION INFORMATION:
It is likely to work with any Java 7, but I only tested with 1.7.0_04
java version "1.7.0_04"
Java(TM) SE Runtime Environment (build 1.7.0_04-b20)
Java HotSpot(TM) Client VM (build 23.0-b21, mixed mode, sharing)
STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
jdk1.8.0_60\bin>javaw -Xmx2000m
EXPECTED VERSUS ACTUAL BEHAVIOR :
EXPECTED -
We expected an error dialog showing a fatal error while launching the JVM.
ACTUAL -
Nothing is shown. Using "java" instead of "javaw" is missing some "Error: xxx" lines.
REPRODUCIBILITY :
This bug can be reproduced always.
java version "1.8.0_60"
Java(TM) SE Runtime Environment (build 1.8.0_60-b27)
Java HotSpot(TM) Client VM (build 25.60-b23, mixed mode, sharing)
ADDITIONAL OS VERSION INFORMATION :
Microsoft Windows [version 10.0.10240]
A DESCRIPTION OF THE PROBLEM :
Java 7 launchers report too large -Xmx as an error while Java 8 does not. We are using the 32 bit versions.
Here are the different scenarios:
jdk1.7.0_04\bin>java -Xmx2000m
-> error message in console:
Error occurred during initialization of VM
Could not reserve enough space for object heap
Error: Could not create the Java Virtual Machine.
Error: A fatal exception has occurred. Program will exit.
jdk1.7.0_04\bin>javaw -Xmx2000m
-> error message in dialog:
Error: Could not create the Java Virtual Machine.
Error: A fatal exception has occurred. Program will exit.
jdk1.8.0_60\bin>java -Xmx2000m
-> error message in console:
Error occurred during initialization of VM
Could not reserve enough space for 2048000KB object heap
jdk1.8.0_60\bin>javaw -Xmx2000m
-> no error message!
This is very problematic because application shortcuts do contain -Xmx which may have to be adjusted with Java 8 (value that was working with Java 7 does not work with Java 8), but when the user clicks, nothing happens and they have no clue why. Before, there was an error dialog for such problems.
REGRESSION. Last worked in version 7u75
ADDITIONAL REGRESSION INFORMATION:
It is likely to work with any Java 7, but I only tested with 1.7.0_04
java version "1.7.0_04"
Java(TM) SE Runtime Environment (build 1.7.0_04-b20)
Java HotSpot(TM) Client VM (build 23.0-b21, mixed mode, sharing)
STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
jdk1.8.0_60\bin>javaw -Xmx2000m
EXPECTED VERSUS ACTUAL BEHAVIOR :
EXPECTED -
We expected an error dialog showing a fatal error while launching the JVM.
ACTUAL -
Nothing is shown. Using "java" instead of "javaw" is missing some "Error: xxx" lines.
REPRODUCIBILITY :
This bug can be reproduced always.
- backported by
-
JDK-8304789 javaw not reporting fatal error (-Xmx too large)
-
- Closed
-