Increased safepoint cleanup tasks in Java 11 (vs 8)

[Milan Mimica]

On Thu, 6 Jun 2019 at 02:41, Daniel D. Daugherty
<daniel.daugherty at oracle.com> wrote:
>
> Java Monitor inflation is caused by:
>
> - contention on the same monitor between 2 or more threads
> - monitor.wait() call
> - synchronized (obj) { obj.hashCode(); }
>
> The last one is specific to the HotSpot VM.

It's the last one more general? hashCode() doesn't have to be invoked
inside the sync block. Like this:
synchronized (obj) { ... }, and later obj.hashCode() revokes biasing.


-- 
Milan Mimica