RFR (S): 7009641: Don't use CodeCache for allocations if it is already full

Vladimir Kozlov vladimir.kozlov at oracle.com
Tue Sep 17 11:10:14 PDT 2013



On 9/17/13 10:44 AM, Albert Noll wrote:
> Hi,
> could I have reviews for this small patch?
> bug: https://bugs.openjdk.java.net/browse/JDK-7009641
> webrev: http://cr.openjdk.java.net/~anoll/7009641/webrev.00/
> <http://cr.openjdk.java.net/%7Eanoll/7009641/webrev.00/>
> Problem:
> If the code cache is full and we try to allocate vtable stubs, we have a
> crash although we could continue execution.
> Solution:
> Since memory from the code cache can be allocated/released by multiple
> threads, the cleanest solution is to let the allocation
> in the code cache return NULL instead of failing the entire VM (for
> vtable stubs). If there is no memory left, no vtable stubs will
> be created and the IC is cleaned.
> Many thanks in advance,
> Albert

More information about the hotspot-compiler-dev mailing list