Lines Matching full:allocation
141 allocation sites at various points in the program, including the point of
142 peak memory allocation. The use of a separate script for presenting the
250 allocation/deallocation, plus a couple of extras. Massif starts by taking
251 snapshots for every heap allocation/deallocation, but as a program runs for
401 an allocation tree which indicates exactly which pieces of code were
406 99.21% (9,000B) (heap allocation functions) malloc/new/new[], --alloc-fns, etc.
410 <para>The allocation tree can be read from the top down. The first line
411 indicates all heap allocation functions such as <function>malloc</function>
415 called? At this point, every allocation so far has been due to line 20
431 99.48% (20,000B) (heap allocation functions) malloc/new/new[], --alloc-fns, etc.
445 the global allocation peak is reached, and a detailed snapshot (number 14)
446 is taken. Its allocation tree shows that 20,000B of useful heap memory has
452 <para>We can then drill down further in the allocation tree. For example,
456 <para>In short, Massif collates the stack trace of every single allocation
506 99.76% (10,000B) (heap allocation functions) malloc/new/new[], --alloc-fns, etc.
568 Heap allocation functions such as <function>malloc</function> are built on
606 (page allocation syscalls) mmap/mremap/brk, --alloc-fns, etc.
612 (heap allocation functions) malloc/new/new[], --alloc-fns, etc.
637 in a particular column, which makes following the allocation chains easier.
707 <para>Maximum depth of the allocation trees recorded for detailed
719 they were a heap allocation function such as
722 which can fill up the allocation trees with uninteresting information.
734 inconvenient, but the reason is that checking for allocation functions
754 <para>Any direct heap allocation (i.e. a call to
782 percentage of total memory size. Allocation tree entries that account
794 allocation peak; by default it records a peak only when the global
795 memory allocation size exceeds the previous peak by at least 1.0%.
796 This is because there can be many local allocation peaks along the way,
