JDK-4903117 : JVMTI spec: heap reference iteration callbacks should allow selective follow
  • Type: Enhancement
  • Component: hotspot
  • Sub-Component: jvmti
  • Affected Version: 5.0
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2003-08-07
  • Updated: 2017-05-16
  • Resolved: 2003-10-13
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
5.0 tigerFixed
Related Reports
Relates :  
Description
Scalability issue --
The object reference graph is huge.  The current specification's
reference callback scheme allows only two choices: recursively iterate all
references or abort.  An agent may know that it doesn't want to follow a
particular reference but not want to abort the entire iteration.  An example:
when using IterateOverObjectsReachableFromObject(jobject) -- each object has
a reference to its class, its class references references its class loader, 
its class loader references all its classes, these classes references the
objects in their static fields, etc.  This chain of reference may not be
interesting to an agent.

Comments
CONVERTED DATA BugTraq+ Release Management Values COMMIT TO FIX: generic FIXED IN: tiger INTEGRATED IN: tiger tiger-b18
14-06-2004

EVALUATION see description and suggested fix
11-06-2004

SUGGESTED FIX Change the callback return value from boolean to a three way enumeration, one of which indicate that the iteration should continue but that references from this object should not be pursued.
11-06-2004