Loading... (original) (raw)
- Type:
Bug
- Resolution: Fixed
- Priority:
P4
- Fix Version/s: 11
- Affects Version/s: 8u161, 9.0.4, 10
- Environment:
Zero on s390
We've found that when building Zero on s390 (note, NOT s390x), the set max heap settings during a build can be problematic. Sometimes builds failed, because the heap couldn't be allocated. It's currently set to 1100M (JDK 8) and 1024M (JDK 9+) which isn't always available on every builder. Our experience has shown that building with the following big workload settings works well:
-Xmx768M -Xms256M
Related downstream bug:
https://icedtea.classpath.org/bugzilla/show_bug.cgi?id=2415
backported by
JDK-8202645 [Zero] Reduce limits of max heap size for boot JDK on s390
- Resolved
JDK-8202778 [Zero] Reduce limits of max heap size for boot JDK on s390
- Resolved
JDK-8202928 [Zero] Reduce limits of max heap size for boot JDK on s390
- Resolved
JDK-8202965 [Zero] Reduce limits of max heap size for boot JDK on s390
- Resolved
JDK-8208839 [Zero] Reduce limits of max heap size for boot JDK on s390
- Resolved
JDK-8216639 [Zero] Reduce limits of max heap size for boot JDK on s390
- Resolved
relates to
JDK-8202784 generated-configure.sh changes missing in 8201495
- Resolved
(1 backported by, 1 relates to)