Lines Matching refs:memory

2 This document describes how to verify the native memory allocator on Android.
7 [Memory Replay Benchmarks](#memory-replay-benchmarks) and
12 called the svelte config, which is designed to run on memory constrained
29 These are functions that are used to implement a memory leak detector
56 allocator will attempt to purge and release any unused memory back to the
78 any unused memory immediately. The argument for this call is ignored. If
79 possible, this call should clear thread cached memory if it exists. The
80 idea is that this can be called to purge memory that has not been
83 application wants to purge that memory before waiting for the next connection.
135 been allocator bugs that cause memory failures when too much virtual
291 These calls are used to free unused memory pages back to the kernel.
314 These benchmarks display RSS, virtual memory consumed (VA space), and do a
355 it takes to make the pointer completely resident in memory is included.
371 There is no specific benchmark for memory fragmentation, instead, the RSS
372 when running the memory traces acts as a proxy for this. An allocator that
392 In addition, in order for the frameworks code to keep track of the memory