RFR(XXS): Event Based tracing framework trace_id's to be reassigned for CDS klasses
stefan.karlsson at oracle.com
Thu Apr 24 16:30:27 UTC 2014
On 2014-04-24 17:42, Markus Grönlund wrote:
> Kindly asking for reviews for the following very small fix:
> Bug: https://bugs.openjdk.java.net/browse/JDK-8041723
> Webrev: http://cr.openjdk.java.net/~mgronlun/8041723/webrev01/
Klass::restore_unshareable_info() might be called multiple times for a
given Klass. This can happen if OutOfMemoryErrors is thrown when the
Klass is loaded, and we later retry to load the Klass. Is it OK to call
TRACE_INIT_ID(this) multiple times for the same Klass?
> The Event Based tracing framework assigns a unique traceid to Klass:es
> for tracking purposes.
> Normally, a new Klass is assigned it's traceid inside the Klass
> For Klass:es coming into the system via the ClassDataSharing (CDS)
> mechanism, the old traceid for the Klass will be stale, hence a "new"
> traceid needs to be (re)assigned to the Klass.
> Thank you
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the hotspot-runtime-dev