Lines Matching full:lock
135 * Grab the lock, but put ourselves into THREAD_VMWAIT if it looks like
215 * lock, wait for the GC to complete, and retrying allocating.
278 * The caller must not be holding the heap lock, or else the allocations
449 * thread stacks. (Before we do so, grab the lock.)
466 /* The heap lock must be held.
534 * Re-acquire the heap lock and perform the final thread
694 * must hold the heap lock.
698 * case we will be suspended with the heap lock held, which can lead to
701 * allocates memory. We can avoid this situation by releasing the lock
708 * activity will grab the lock before issuing a suspend-all. (We may briefly
