RFR: Mark-compact and heuristics should consistently process refs and unload classes

Roman Kennke rkennke at redhat.com
Tue May 30 08:43:45 UTC 2017


Am 30.05.2017 um 10:28 schrieb Aleksey Shipilev:
> On 05/30/2017 09:59 AM, Aleksey Shipilev wrote:
>> We have copied the random block from Aggressive policy to Passive one. The goal
>> for random selection in Aggressive is to exercise all paths. For Passive, we are
>> better off being consistent:
> Actually, let's also cover mark-compact parts:
>   http://cr.openjdk.java.net/~shade/shenandoah/passive-ur-cu/webrev.01/
>
> -Aleksey
>
I am not sure about this. I think the intention of the flags controlling
ref processing and class unloading were meant to affect regular GC
cycles. Mark-compact is our last-ditch collection and should always
process refs and unload classes. What would be a good reason to not do that?


Roman



More information about the shenandoah-dev mailing list