JDK-4988100 : oop_verify_old_oop appears to be dead
  • Type: Enhancement
  • Component: hotspot
  • Sub-Component: gc
  • Affected Version: hs22,5.0
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • OS: generic,solaris_8
  • CPU: generic,sparc
  • Submitted: 2004-02-04
  • Updated: 2013-06-26
  • Resolved: 2012-04-25
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 7 JDK 8 Other
7u40Fixed 8Fixed hs24Fixed
Related Reports
Duplicate :  
I was curious what the allow_dirty flag, which is carefully passed through quite a few layers of verify calls, actually controlled so I walked down the call chain.  The only potential uses of the flag appear to be in Klass::oop_verify_old_oop and objArrayKlass::oop_verify_old_oop, both of whose bodies are completely commented out.  It might be nice to completely delete this useless flag and method.

EVALUATION http://hg.openjdk.java.net/lambda/lambda/hotspot/rev/b632e80fc9dc

EVALUATION http://hg.openjdk.java.net/hsx/hotspot-gc/hotspot/rev/b632e80fc9dc

EVALUATION fix for mustang. ###@###.### 2004-12-09 20:10:53 GMT

CONVERTED DATA BugTraq+ Release Management Values COMMIT TO FIX: dragon