-
Bug
-
Resolution: Fixed
-
P3
-
21.0.2, 22, 23, repo-lilliput-17
-
b09
The method
'
ObjectMonitor* ObjectSynchronizer::inflate(Thread* current, oop object, const InflateCause cause)
'
expect to be invoked with the current thread.
However in the method
Deoptimization::relock_objects()
it is executed with deoptee thread.
See:
https://github.com/openjdk/jdk/blob/master/src/hotspot/share/runtime/deoptimization.cpp#L1650
'
ObjectMonitor* ObjectSynchronizer::inflate(Thread* current, oop object, const InflateCause cause)
'
expect to be invoked with the current thread.
However in the method
Deoptimization::relock_objects()
it is executed with deoptee thread.
See:
https://github.com/openjdk/jdk/blob/master/src/hotspot/share/runtime/deoptimization.cpp#L1650
- relates to
-
JDK-8318895 Deoptimization results in incorrect lightweight locking stack
- Resolved
-
JDK-8227745 Enable Escape Analysis for Better Performance in the Presence of JVMTI Agents
- Resolved
- links to
-
Commit openjdk/jdk/a3a2b1fb
-
Commit openjdk/lilliput-jdk17u/517053dd
-
Commit openjdk/lilliput-jdk21u/c7e855dc
-
Review openjdk/jdk/17626
-
Review openjdk/lilliput-jdk17u/81
-
Review openjdk/lilliput-jdk21u/22
(3 links to)