-
Bug
-
Resolution: Fixed
-
P4
-
hs10
-
b01
-
generic
-
generic
-
Not verified
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-2177098 | 7 | Erik Trimble | P3 | Resolved | Fixed | b27 |
| JDK-2174906 | 6u14 | Abhijit Saha | P3 | Resolved | Fixed | b01 |
closed/compiler/6321689/Test.java fails with
"java.lang.OutOfMemoryError: Java heap space" with 64-bit jvm in case non-Parallel GCs are used.
The problem is that the test requires about 100M to run.
However, the default heap size in case of non-parallel GC is set to 84Mb
(you can attach jmap to see it).
The default heap size for Parallel GCs is calculated based on amount of available RAM,
so in case of 2Gb the max heap size is set to 512 Mb.
This is why the test doesn't fail with Parallel GCs.
The test needs to be adjusted to run with all collectors or default max heap size
for server-class machines need to be rethinking for non-parallel GCs.
"java.lang.OutOfMemoryError: Java heap space" with 64-bit jvm in case non-Parallel GCs are used.
The problem is that the test requires about 100M to run.
However, the default heap size in case of non-parallel GC is set to 84Mb
(you can attach jmap to see it).
The default heap size for Parallel GCs is calculated based on amount of available RAM,
so in case of 2Gb the max heap size is set to 512 Mb.
This is why the test doesn't fail with Parallel GCs.
The test needs to be adjusted to run with all collectors or default max heap size
for server-class machines need to be rethinking for non-parallel GCs.
- backported by
-
JDK-2174906 TEST_BUG: closed/compiler/6321689/Test.java fails with OOM with 64-bit jvm with non-Parallel GCs
-
- Resolved
-
-
-
- Resolved
-