On Wed, 30 Apr 2025 11:25:34 GMT, Alan Bateman <al...@openjdk.org> wrote:

> Hopefully David will remember more of this when he gets back.

Sadly I have to page in all the details again like everyone else.

The underlying issue is nested-parking as Alan notes. From re-reading 8074773, 
pre-loading in any class loaded by the boot loader, has no affect on the bug. 
The issue was the action taken by the AppLoader that involved creating an entry 
in the lockMap CHM. That particular bug-path was closed when CHM was rewritten 
to use object monitors (did it re-open again when Loom came along?).

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

PR Comment: https://git.openjdk.org/jdk/pull/24952#issuecomment-2864931853

Reply via email to