Lines Matching full:leaked
547 the pointer to a leaked block was lost; you have to work that out for
568 leaked blocks and/or give
1571 detailed information for each leak: the stack trace where the leaked blocks
1572 were allocated, the number of blocks leaked and their total size. When a
1597 possibly leaked blocks, .i.e those for which only an interior
1612 allocation stacks with an increased number of leaked bytes or
1626 the leaked bytes. The second command is the same as the first
1780 in command <code class="varname">block_list</code>) is shown before the tree was leaked.
1867 entries for which there was an increase in leaked bytes or leaked
1872 entries for which there was an increase or decrease in leaked
1873 bytes or leaked number of blocks since the previous leak search. It
1881 leak check to be leaked (i.e. the sum of direct leaks and indirect leaks),
