Integrated: 8244679: JVM/TI GetCurrentContendedMonitor/contmon001 failed due to "(IsSameObject#3) unexpected monitor object: 0x000000562336DBA8"

[Robbin Ehn]

On Wed, 11 Nov 2020 20:33:15 GMT, Robbin Ehn <rehn at openjdk.org> wrote:

> As the stack trace in the bug shows, we cannot load classes, since we may take a monitor.
> Resulting in an unexpected result to GetCurrentContendedMonitor().
> Trying to use some decent primitive, e.g. Wicket/Semaphore/.., without being implementation dependent means we must warm up every possible scenario, since it may use a new class.
> Instead I here just use sleep + volatile for the barriers.
> 
> I cannot reproduce with these changes.
> 
> Chewing through T6 as most issues have been seen there - passed.

This pull request has now been integrated.

Changeset: c5fe2c1f
Author:    Robbin Ehn <rehn at openjdk.org>
URL:       https://git.openjdk.java.net/jdk/commit/c5fe2c1f
Stats:     36 lines in 2 files changed: 22 ins; 5 del; 9 mod

8244679: JVM/TI GetCurrentContendedMonitor/contmon001 failed due to "(IsSameObject#3) unexpected monitor object: 0x000000562336DBA8"

Reviewed-by: pchilanomate, dcubed, dholmes, sspitsyn

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

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