RFR: 8274794: Print all owned locks in hs_err file

[Coleen Phillimore]

On Fri, 15 Oct 2021 08:27:24 GMT, Thomas Stuefe <stuefe at openjdk.org> wrote:

>> I think the view is that the static mutexes will populate from the start of the array so any dynamic mutex, which is the only candidate for removal, must be closer to the end.
>
>> I think the view is that the static mutexes will populate from the start of the array so any dynamic mutex, which is the only candidate for removal, must be closer to the end.
> 
> That's what I understood too. But there can be a ton of dynamic Mutexes, so this does not really help that much.

Yes. That's what my logging found.  There are a set of 100 or so static mutexes and then we have startThread_lock which is very short lived, TaskTermination_lock and HandshakeState_lock per thread.  The latter isn't that short lived.

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

PR: https://git.openjdk.java.net/jdk/pull/5958