8351359: OperatingSystemMXBean: values from getCpuLoad and getProcessCpuLoad are stale after 24.8 days (Windows) #701
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi,
It's a clean backport of JDK-8351359.
I didn't include
#include <sysinfoapi.h>
as it is in the original commit because of compilation problem.Instead of that, there is already included
windows.h
that contains theGetTickCount64()
function. It's redundant to includesysinfoapi.h
.The changes are related to Windows only.
Testing:
getProcessCpuLoad()
on windows server 2025, intel cpuProgress
Error
Issue
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk8u-dev.git pull/701/head:pull/701
$ git checkout pull/701
Update a local copy of the PR:
$ git checkout pull/701
$ git pull https://git.openjdk.org/jdk8u-dev.git pull/701/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 701
View PR using the GUI difftool:
$ git pr show -t 701
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk8u-dev/pull/701.diff