On Fri, 21 Jun 2024 14:05:51 GMT, Kevin Walls wrote:
> Man page update for JDK-8327793 which marked jstatd as deprecated for removal
> in JDK 24.
Sorry this got left "pending" yesterday
src/jdk.jstatd/share/man/jstatd.1 line 49:
> 47: future release.
> 48: .PP
> 49: \f[B]Note:\f[R] This comma
Hi all,
This PR addresses [8332124](https://bugs.openjdk.org/browse/JDK-8332124)
enabling jcmd to accept "help" as an argument to subcommands.
Testing:
- [x] Verified running `jcmd 4711 VM.metaspace help` works along with other
subcommands.
- [x] Added test case passes.
Thanks,
Sonia
--
On Wed, 5 Jun 2024 06:22:17 GMT, Sebastian Lövdahl wrote:
>> 8327114: Attach in Linux may have wrong behaviour when pid == ns_pid
>> (Kubernetes debug container)
>
> Sebastian Lövdahl has updated the pull request incrementally with one
> additional commit since the last revision:
>
> Add tes
On Fri, 17 May 2024 19:32:31 GMT, Chris Plummer wrote:
>> This PR adds ranked monitor support to the debug agent. The debug agent has
>> a large number of monitors, and it's really hard to know which order to grab
>> them in, and for that matter which monitors might already be held at any
>> g
Hi all,
After [JDK-8294960](https://bugs.openjdk.org/browse/JDK-8294960), the
footprint memory usage increased significantly when run the testcase with
-Xcomp jvm options, then cause the testcase was killed by docker by OOM.
Maybe the footprint memory usage increased was inevitable, so I thin
The tool to examine HotSpot crashes has been published as a plugin:
https://plugins.jetbrains.com/plugin/24675-hotspot-crash-examiner
Its source code is fully open:
https://github.com/JetBrains/HotSpotCrashExaminerPlugin
I hope the community around HotSpot will find it useful.
On Wed, Apr 24, 20
On Fri, 21 Jun 2024 14:05:51 GMT, Kevin Walls wrote:
> Man page update for JDK-8327793 which marked jstatd as deprecated for removal
> in JDK 24.
I assume we should hold off reviewing until the warning and the experiment note
are combined.
-
PR Comment: https://git.openjdk.org/jd
On Sat, 22 Jun 2024 00:18:43 GMT, Coleen Phillimore wrote:
> The 'resolve' for the CLDG iterator was to temporarily keep that CLD from
> being unloaded, in the short time that we're iterating on that particular CLD.
This is the crux of the problem. For concurrent GCs, if the 'resolve' is calle
