RFR(S): 8203664: JFR start failure after AppCDS archive created with JFR StartFlightRecording
calvin.cheung at oracle.com
Wed Jun 20 18:18:48 UTC 2018
Corrected the bug id in the subject and also the link to webrev:
(Note: 8203*6*64 instead of 8203*3*64)
On 6/20/2018 11:04 AM, Calvin Cheung wrote:
> bug: https://bugs.openjdk.java.net/browse/JDK-8203664
> webrev: http://cr.openjdk.java.net/~ccheung/8203364/webrev.00/
> The bug is due to some classes are being redefined during JFR startup.
> The proposed change is to handle redefined classes better during dump
> Summary of changes:
> Only do the following assert if a class hasn't been redefined:
> 244 assert(cached_class_file == NULL, "Sanity");
> include JFR classes which are loaded via 'JVM_DefineClass'
> during dumping, exclude classes which have been redefined.
> Only very few classes are being redefined with JFR enabled during
> The change passed hs-tier[1,2,3] testing.
More information about the hotspot-runtime-dev