[jdk16] RFR: 8259063: Possible deadlock with vtable/itable creation vs concurrent class unloading [v2]

[Erik Österlund]

On Tue, 12 Jan 2021 15:42:14 GMT, Nils Eliasson <neliasso at openjdk.org> wrote:

>> Erik Österlund has updated the pull request incrementally with one additional commit since the last revision:
>> 
>>   don't handle code cache exhaustion fully during inline cache patching
>
> I like the solution - simple and without adding extra complexity or lock juggling.
> 
> It's a good just skipping the call to handle_full_code_cache. The VTableBlobs are not the thing usually filling up the code cache - and they can be placed in any codeheap. And even if we skip it - no harm done - there will be other allocations that will trigger the call.

Thanks for the reviews @neliasso and @pliden.

-------------

PR: https://git.openjdk.java.net/jdk16/pull/103