Lines Matching refs:memory

1 Triggering the GC to reclaim non-Java memory
14 allocated Java objects in the Java heap, even if they "own" large amounts of C++ memory, which
19 certain amount of C++ memory had been allocated, and could only be reclaimed as the result of a
22 This had the advantage that the GC would theoretically know exactly how much native memory was
31 In extreme cases, underestimation of native object sizes could cause native memory use to be so
39 memory has been allocated, and assumes that any of this may need the collector's help to reclaim.
40 C++ memory allocated by means other than `malloc`/`new` and owned by Java objects should still be
48 We normally check for the need to trigger a GC due to native memory pressure only as a result of
69    `NativeAllocationRegistry`. (The computation also considers the total amount of native memory
75 currently occupies a large fraction of device memory, suggesting that the GC is falling behind and
78 The fact that we consider both Java and native memory use at once means that we are more likely to