RFC: Safe OOM during evac

[Roman Kennke]

Am 20.10.2017 um 15:35 schrieb Zhengyu Gu:
>>> Is this the direction we are heading? 'cause I would need to revive 
>>> pin_object() patch
>> Currently we're heading nowhere :-) I'm building a prototype to try 
>> to make a safe OOM-during-evac handling. If string dedup does modify 
>> evacuated objects, I'll make this safe OOM-during-evac handling for 
>> GC workers too. That should resolve your problem, right?
>
> Probably not, 'cause it still sees from-space pointers.
This is a complete and according to my stress-tests stable patch. It 
also includes a fix for the pinning problem. It also enables this 
safe-oom-during-evac by default (should probably default to false for 
later pushing).

http://cr.openjdk.java.net/~rkennke/safe-oom-during-evac/webrev.01/ 
<http://cr.openjdk.java.net/%7Erkennke/safe-oom-during-evac/webrev.01/>

Roman