The ClassUnload event should be removed from JVMTI.
It's existence in JVMDI has been a stablity issue.
It was relucantly incl;uded in JVMTI in order to support JVMDI.
There is no independent need for ClassUnload events in JVMTI since
it has much more powerful functionality.
A new mechanism to generate the JVMDI events has been discovered,
so they now be removed from JVMTI.
It's existence in JVMDI has been a stablity issue.
It was relucantly incl;uded in JVMTI in order to support JVMDI.
There is no independent need for ClassUnload events in JVMTI since
it has much more powerful functionality.
A new mechanism to generate the JVMDI events has been discovered,
so they now be removed from JVMTI.
- relates to
-
JDK-4639363 Java Platform Profiling Architecture (JSR-163)
-
- Resolved
-