RFR: 8244679: JVM/TI GetCurrentContendedMonitor/contmon001 failed due to "(IsSameObject#3) unexpected monitor object: 0x000000562336DBA8" [v3]
Robbin Ehn
rehn at openjdk.java.net
Mon Nov 16 08:36:09 UTC 2020
> 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.
Robbin Ehn has updated the pull request incrementally with one additional commit since the last revision:
Removed dummy sleeps
-------------
Changes:
- all: https://git.openjdk.java.net/jdk/pull/1177/files
- new: https://git.openjdk.java.net/jdk/pull/1177/files/32879e2d..5fc31ebd
Webrevs:
- full: https://webrevs.openjdk.java.net/?repo=jdk&pr=1177&range=02
- incr: https://webrevs.openjdk.java.net/?repo=jdk&pr=1177&range=01-02
Stats: 3 lines in 2 files changed: 0 ins; 3 del; 0 mod
Patch: https://git.openjdk.java.net/jdk/pull/1177.diff
Fetch: git fetch https://git.openjdk.java.net/jdk pull/1177/head:pull/1177
PR: https://git.openjdk.java.net/jdk/pull/1177
More information about the serviceability-dev
mailing list