Home
last modified time | relevance | path

Searched refs:garbage (Results 1 – 8 of 8) sorted by relevance

/art/runtime/gc/accounting/
Dspace_bitmap.cc218 uintptr_t garbage = in SweepWalk() local
220 buffer_size += POPCOUNT(garbage); in SweepWalk()
228 uintptr_t garbage = in SweepWalk() local
230 if (UNLIKELY(garbage != 0)) { in SweepWalk()
233 const size_t shift = CTZ(garbage); in SweepWalk()
234 garbage ^= (static_cast<uintptr_t>(1)) << shift; in SweepWalk()
236 } while (garbage != 0); in SweepWalk()
/art/test/175-alloc-big-bignums/
Dinfo.txt3 the garbage collector often enough to prevent us from running out of memory.
7 triggered by Java garbage collection.
/art/test/074-gc-thrash/
Dinfo.txt1 This thrashes the memory allocator and garbage collector for a brief period.
/art/test/072-reachability-fence/
Dinfo.txt1 Check that reachabilityFence() prevents garbage collection of objects only referred to by a dead
/art/test/109-suspend-check/
Dinfo.txt1 To support garbage collection, debugging and profiling the VM must be able to send all threads
/art/test/1945-proxy-method-arguments/
Dinfo.txt6 object may have been moved by the garbage collector, but the stack
/art/test/109-suspend-check/src/
DMain.java210 byte[] garbage = new byte[100000]; in run()
/art/runtime/
Dmutator_gc_coord.md4 Most garbage collection work can proceed concurrently with the client or
6 thread stacks, the garbage collector needs to ensure that Java data processed
8 should not hold references to the heap that are invisible to the garbage
33 logically releases the mutator lock. When the garbage collector needs mutator