Lines Matching refs:Java

1 Triggering the GC to reclaim non-Java memory
5 effectively owned by a Java object, and reclaimed when the garbage collector determines that the
6 owning Java object is no longer reachable. Various mechanisms are used to accomplish this. These
7 include traditional Java finalizers, more modern Java `Cleaner`s, Android's `SystemCleaner` and,
12 Java objects of significantly smaller size. The Java garbage collector normally decides when to
13 collect based on occupancy of the Java heap. It would not collect if there are few bytes of newly
14 allocated Java objects in the Java heap, even if they "own" large amounts of C++ memory, which
15 cannot be reclaimed until the Java objects are reclaimed.
20 Java GC.
23 owned by Java objects. However, its major problem was that registering the exact size of such
24 native objects frequently turned out to be impractical. Often a Java object does not just own a
27 be shared between Java objects, and could only be reclaimed when all of those Java objects became
34 digits backing Java `BigInteger`s to force a restart of system processes. (This has since been
40 C++ memory allocated by means other than `malloc`/`new` and owned by Java objects should still be
41 explicitly registered. This loses information about Java ownership, but results in much more
59 1. An adjusted heap size for GC triggering. This consists of the Java heap size at which we would
67    allocated in the Java heap, plus half the net number of native bytes allocated since the last
81 The fact that we consider both Java and native memory use at once means that we are more likely to
82 trigger a native GC when we are closer to the normal Java GC threshold.