On Sat, 13 Jan 2024 18:06:11 GMT, Alan Bateman wrote:
> Clean backport of P3 issue JDK-8322846.
Marked as reviewed by jpai (Reviewer).
-
PR Review: https://git.openjdk.org/jdk22/pull/71#pullrequestreview-1822387922
Clean backport of P3 issue JDK-8322846.
-
Commit messages:
- Backport faa9c6909dda635eb008b9dada6e06fca47c17d6
Changes: https://git.openjdk.org/jdk22/pull/71/files
Webrev: https://webrevs.openjdk.org/?repo=jdk22=71=00
Issue: https://bugs.openjdk.org/browse/JDK-8322846
Stats:
On Thu, 4 Jan 2024 12:53:07 GMT, Alan Bateman wrote:
>> -Djdk.tracePinnedThreads is a debugging option that dates from early
>> development in the loom repo to identify pinned threads. It has several
>> issues and this tracing option will eventually be removed (use the JFR
>> events instead).
> -Djdk.tracePinnedThreads is a debugging option that dates from early
> development in the loom repo to identify pinned threads. It has several
> issues and this tracing option will eventually be removed (use the JFR events
> instead). Several hangs have been reported when running with the
On Tue, 2 Jan 2024 13:53:39 GMT, Alan Bateman wrote:
> -Djdk.tracePinnedThreads is a debugging option that dates from early
> development in the loom repo to identify pinned threads. It has several
> issues and this tracing option will eventually be removed (use the JFR events
> instead).
On Tue, 2 Jan 2024 13:53:39 GMT, Alan Bateman wrote:
> -Djdk.tracePinnedThreads is a debugging option that dates from early
> development in the loom repo to identify pinned threads. It has several
> issues and this tracing option will eventually be removed (use the JFR events
> instead).
On Tue, 2 Jan 2024 13:53:39 GMT, Alan Bateman wrote:
> -Djdk.tracePinnedThreads is a debugging option that dates from early
> development in the loom repo to identify pinned threads. It has several
> issues and this tracing option will eventually be removed (use the JFR events
> instead).
On Tue, 2 Jan 2024 15:56:06 GMT, Jaikiran Pai wrote:
> I guess that then means that the some pinned threads might not even appear in
> this generated thread dumps.
Just to be clear. The changes here have no impact on thread dumps, the thread
dump generated by jcmd Thread.dump_to_file has all
On Tue, 2 Jan 2024 13:53:39 GMT, Alan Bateman wrote:
> -Djdk.tracePinnedThreads is a debugging option that dates from early
> development in the loom repo to identify pinned threads. It has several
> issues and this tracing option will eventually be removed (use JFR events
> instead). Several
-Djdk.tracePinnedThreads is a debugging option that dates from early
development in the loom repo to identify pinned threads. It has several issues
and this tracing option will eventually be removed (use JFR events instead).
Several hangs have been reported when running with the system property
10 matches
Mail list logo
