JDK-8164692 : InstanceKlass::_previous_version_count goes negative
  • Type: Bug
  • Component: hotspot
  • Sub-Component: jvmti
  • Affected Version: 9
  • Priority: P3
  • Status: Closed
  • Resolution: Fixed
  • Submitted: 2016-08-23
  • Updated: 2016-09-22
  • Resolved: 2016-08-31
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.
JDK 9
9 b137Fixed
Related Reports
Relates :  
JDK-8156137 - SIGSEGV in ReceiverTypeData::clean_weak_klass_links
Relates :  
JDK-8165246 - [REDO] InstanceKlass::_previous_version_count goes negative
Description
While investigating 8156137 I noticed that InstanceKlass::_previous_version_count goes negative unexpectedly.  There seems to be an accounting problem.
Comments
Moving from hotspot/runtime -> hotspot/jvmti. The previous version count is used by JVM/TI RedefineClasses() so this bug belongs with other JVM/TI bugs...
30-08-2016
_previous_version_count very wrong.
26-08-2016
This may be part of the root cause of 8156137. After I put in a tentative fix for _previous_version_count, the 8156137 crash isn't reproducing.
25-08-2016