jmx-dev RFR: 8351359: OperatingSystemMXBean: values from getCpuLoad and getProcessCpuLoad are stale after 24.8 days (Windows) [v2]

Kevin Walls kevinw at openjdk.org
Wed May 7 11:25:32 UTC 2025


> OperatingSystemImpl.c on Windows is limited by its use of clock(), which hits its limit with longer process uptimes.
> 
> https://learn.microsoft.com/en-us/cpp/c-runtime-library/reference/clock?view=msvc-170
> "maximum clock function return value of 2147483.647 seconds, or about 24.8 days"
> 
> The linked alternative, time(), gives 64-bit time but only seconds.  In the example code for time(), there is use of _ftime() to retrieve milliseconds.
> 
> The example code also notes that _ftime is deprecated, so _ftime_s is used here.

Kevin Walls has updated the pull request incrementally with one additional commit since the last revision:

  Use GetTickCount64

-------------

Changes:
  - all: https://git.openjdk.org/jdk/pull/25062/files
  - new: https://git.openjdk.org/jdk/pull/25062/files/3dd8362f..c7861219

Webrevs:
 - full: https://webrevs.openjdk.org/?repo=jdk&pr=25062&range=01
 - incr: https://webrevs.openjdk.org/?repo=jdk&pr=25062&range=00-01

  Stats: 5 lines in 1 file changed: 0 ins; 3 del; 2 mod
  Patch: https://git.openjdk.org/jdk/pull/25062.diff
  Fetch: git fetch https://git.openjdk.org/jdk.git pull/25062/head:pull/25062

PR: https://git.openjdk.org/jdk/pull/25062


More information about the jmx-dev mailing list