JDK-8035292 : Discontinue hprof format from reporting signers and protection domains in classes
  • Type: Enhancement
  • Component: hotspot
  • Sub-Component: svc
  • Affected Version: 9
  • Priority: P4
  • Status: Closed
  • Resolution: Won't Fix
  • Submitted: 2014-02-19
  • Updated: 2016-12-14
  • Resolved: 2016-12-14
Related Reports
Blocks :  
JDK-8003551 - Move Signers out to the JDK
Description
We are proposing changing the implementation java/lang/Class.getSigners and setSigners to not require a signers field per class (which is currently injected by the JVM) to save footprint.  This change requires that we discontinue support for reporting the signers object ID in hprof format per class.

For protection domains, the proposed change will expose this field as a private field in java/lang/Class so normal hprof heap walking will find this field.

Proposed change to the hprof spec:  jdk/src/share/demo/jvmti/hprof/manual.html is
http://cr.openjdk.java.net/~coleenp/manual.html
Comments
This is not on our list of current priorities. If this changes, please reopen this issue.
14-12-2016
We can't move signers to a hashtable if they are expected to be reported by hprof. We could keep the hprof format and have the field zero for compatibility.
16-09-2014