-
Bug
-
Resolution: Fixed
-
P3
-
11.0.5-oracle, 13, 14
-
b10
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8245301 | 13.0.4 | Chris Plummer | P3 | Resolved | Fixed | b02 |
JDK-8234291 | 11.0.7-oracle | Vaibhav Choudhary | P3 | Resolved | Fixed | b01 |
JDK-8236767 | 11.0.7 | Chris Plummer | P3 | Resolved | Fixed | b01 |
Both of these tests run with -Xmx8g:
TestHeapDumpForLargeArray.java and
ClhsdbRegionDetailsScanOopsForG1.java
The make files calculates a MaxRAMPercentage based on the calculated test concurrency. When running these tests with concurrency, we risk running out of memory, the suggested solution is to make sure at least these tests don't run concurrently by using the exclusiveAccess feature in JTreg.
TestHeapDumpForLargeArray.java and
ClhsdbRegionDetailsScanOopsForG1.java
The make files calculates a MaxRAMPercentage based on the calculated test concurrency. When running these tests with concurrency, we risk running out of memory, the suggested solution is to make sure at least these tests don't run concurrently by using the exclusiveAccess feature in JTreg.
- backported by
-
JDK-8234291 Some tests in serviceability/sa run with fixed -Xmx values and risk running out of memory
-
- Resolved
-
-
JDK-8236767 Some tests in serviceability/sa run with fixed -Xmx values and risk running out of memory
-
- Resolved
-
-
JDK-8245301 Some tests in serviceability/sa run with fixed -Xmx values and risk running out of memory
-
- Resolved
-