Problematic use of setAccessible

Aleksey Shipilev shade at
Thu Sep 15 15:46:09 UTC 2016

On 09/15/2016 02:32 PM, Claes Redestad wrote:
> On 2016-09-15 13:37, Aleksey Shipilev wrote:
>> On 09/15/2016 11:35 AM, Claes Redestad wrote:
>>> Sure, but there'd still be a documented way around it. Maybe we should
>>> catch InaccessibleObjectException[1], print a warning/pointer to
>>> workarounds, then move on with Charset.defaultCharset()?
>> I think we can plug the leak that way for a time being:
>> Unfortunately, can't test jake now (slow internet connection), can you
>> try it?
> Looks good to me, perfasm arrows and everything.

Thanks! Verified locally as well. Fixed:


More information about the jmh-dev mailing list