Lines Matching full:objects

16 * application memory (i.e., memory for objects created by applications)
233 It is a region-based allocator, i.e., all objects allocated in region/arena can be efficiently deal…
272 Small objects are joined in "runs" (not individual element for each size, but some "containers" wit…
275 | header for run of objects with size X| obj with size X | free mem size X | ... | obj with size X |
279 Large objects are not joined in "runs".
281 Humongous objects can be allocated by simply proxying requests to the OS (but keeping reference to …
285 Each thread maintains a cache for objects (at least for all objects with small size).
320      - Humongous objects space
325   - Humongous objects space (optional)
387 Since one of the metric for this GC - high throughput, most objects in the Eden will live long enou…
389 …xperiments. As an alternative, we can introduce some average age metadata for run of small objects.
393 1. Mark Eden and move alive objects to the tenured (or survivor)
403 1. Remark missed during concurrent marking objects (STW #2)
432 - humongous regions (for humongous objects)
441 1. Marking young generation + Reference processor + moving alive objects to the tenured space
501 For each safepoint, we should have a method that can provide GC with information about objects on t…
514 …| method that prepares data about objects on stack for the #X safepoint and waits until STW ends |…
529 Heap inconsistency can happen when a GC reclaims alive/reachable objects.
530 I.e. Alive/reachable objects should be reclaimed in the following two conditions: