-
Bug
-
Resolution: Fixed
-
P4
-
None
-
b07
-
x86
-
linux
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8304240 | 17.0.8-oracle | Ivan Bereziuk | P4 | Resolved | Fixed | b01 |
JDK-8300859 | 17.0.7 | Severin Gehwolf | P4 | Resolved | Fixed | b01 |
JDK-8304241 | 11.0.20-oracle | Ivan Bereziuk | P4 | Resolved | Fixed | b01 |
JDK-8301062 | 11.0.19 | Severin Gehwolf | P4 | Resolved | Fixed | b01 |
JDK-8300662 | openjdk8u372 | Jonathan Dowland | P4 | Resolved | Fixed | b01 |
JDK-8304236 | 8u381 | Ivan Bereziuk | P4 | Resolved | Fixed | b01 |
On a system with 7281311744 bytes of total memory the function would return: -1308622848 suggesting some overflow occurring.
This was caught with the tier1 test:
TestMemoryAwareness.testContainerMemExceedsPhysical.
See this discussion on GitHub for further details
https://github.com/openjdk/jdk8u-dev/pull/220#pullrequestreview-1247595245
- backported by
-
JDK-8300662 CgroupMetrics.getTotalMemorySize0() can report invalid results on 32 bit systems
-
- Resolved
-
-
JDK-8300859 CgroupMetrics.getTotalMemorySize0() can report invalid results on 32 bit systems
-
- Resolved
-
-
JDK-8301062 CgroupMetrics.getTotalMemorySize0() can report invalid results on 32 bit systems
-
- Resolved
-
-
JDK-8304236 CgroupMetrics.getTotalMemorySize0() can report invalid results on 32 bit systems
-
- Resolved
-
-
JDK-8304240 CgroupMetrics.getTotalMemorySize0() can report invalid results on 32 bit systems
-
- Resolved
-
-
JDK-8304241 CgroupMetrics.getTotalMemorySize0() can report invalid results on 32 bit systems
-
- Resolved
-
- relates to
-
JDK-8292541 [Metrics] Reported memory limit may exceed physical machine memory
-
- Resolved
-
- links to
-
Commit openjdk/jdk8u-dev/8d2f7e0c
-
Commit openjdk/jdk11u-dev/684a870e
-
Commit openjdk/jdk17u-dev/571f5f5a
-
Commit openjdk/jdk/dea58efb
-
Review openjdk/jdk8u-dev/220
-
Review openjdk/jdk11u-dev/1672
-
Review openjdk/jdk17u-dev/1086
-
Review openjdk/jdk/12069