JDK-8272800 : vmTestbase/nsk/jvmti/RedefineClasses/StressRedefineWithoutBytecodeCorruption/TestDescription.java timing out
  • Type: Bug
  • Component: hotspot
  • Sub-Component: jvmti
  • Affected Version: 18
  • Priority: P4
  • Status: Closed
  • Resolution: Duplicate
  • OS: linux,os_x
  • CPU: x86_64,aarch64
  • Submitted: 2021-08-20
  • Updated: 2021-11-18
  • Resolved: 2021-11-16
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
Other
tbdResolved
Related Reports
Duplicate :  
Sub Tasks
JDK-8276367 :  
JDK-8276368 :  
JDK-8276369 :  
Description
[211.031s][trace][redefine,class,iklass,purge] previous version stats: live=66, deleted=14
Timeout refired 1200 times
Comments
This is a duplicate of JDK-8276177.
16-11-2021

There's definitely something wrong with this InstanceKlass::is_being_redefined() flag. I think as a bit, in an int field, it needs to be set and tested atomicly.
15-11-2021

There are two linked sightings (so far) and both are with -XX:+UseZGC.
25-08-2021