IBM User Guide for Java V7 on Windows > IBM SDK for Java > The collector and the allocator > Allocation

Heap lock allocation

Heap lock allocation occurs when the allocation request cannot be satisfied in the existing cache.

As the name implies, heap lock allocation requires a lock and is therefore avoided, if possible, by using the cache. For a description of cache allocation, see Cache allocation

If the Garbage Collector cannot find a large enough chunk of free storage, allocation fails and the Garbage Collector must run a garbage collection. After a garbage collection cycle, if the Garbage Collector created enough free storage, it searches the freelist again and picks up a free chunk. The heap lock is released either after the object is allocated, or if not enough free space is found. If the Garbage Collector does not find enough free storage, it returns OutOfMemoryError.

Parent: Allocation

Error 404 - Not Found

The document you are looking for may have been removed or re-named. Please contact the web site owner for further assistance.