Searched refs:garbage (Results 1 – 10 of 10) sorted by relevance
220 uintptr_t garbage = in SweepWalk() local222 buffer_size += POPCOUNT(garbage); in SweepWalk()230 uintptr_t garbage = in SweepWalk() local232 if (UNLIKELY(garbage != 0)) { in SweepWalk()235 const size_t shift = CTZ(garbage); in SweepWalk()236 garbage ^= (static_cast<uintptr_t>(1)) << shift; in SweepWalk()238 } while (garbage != 0); in SweepWalk()
3 the garbage collector often enough to prevent us from running out of memory.7 triggered by Java garbage collection.
1 This thrashes the memory allocator and garbage collector for a brief period.
1 Check that reachabilityFence() prevents garbage collection of objects only referred to by a dead
1 To support garbage collection, debugging and profiling the VM must be able to send all threads
6 object may have been moved by the garbage collector, but the stack
210 byte[] garbage = new byte[100000]; in run()
5 effectively owned by a Java object, and reclaimed when the garbage collector determines that the8 for platform code, `NativeAllocationRegistry`. Internally, these all rely on the garbage12 Java objects of significantly smaller size. The Java garbage collector normally decides when to
4 Most garbage collection work can proceed concurrently with the client or6 thread stacks, the garbage collector needs to ensure that Java data processed8 should not hold references to the heap that are invisible to the garbage33 logically releases the mutator lock. When the garbage collector needs mutator104 equivalent: In particular, we rely on the garbage collector never actually227 running the garbage collector and conceivably thus cause it to block. This
16 (With the Concurrent Copying garbage collector, the `LockWord` supports another "forwarding