Options

Counts the number of calls to owns.

Counts the number of calls to allocate. All calls are counted, including requests for zero bytes or failed requests.

Counts the number of calls to allocate that succeeded, i.e. they returned a block as large as requested. (N.B. requests for zero bytes count as successful.)

Counts the number of calls to expand, regardless of arguments or result.

Counts the number of calls to expand that resulted in a successful expansion.

Counts the number of calls to reallocate, regardless of arguments or result.

Counts the number of calls to reallocate that succeeded. (Reallocations to zero bytes count as successful.)

Counts the number of calls to reallocate that resulted in an in-place reallocation (no memory moved). If this number is close to the total number of reallocations, that indicates the allocator finds room at the current block's end in a large fraction of the cases, but also that internal fragmentation may be high (the size of the unit of allocation is large compared to the typical allocation size of the application).

Counts the number of calls to deallocate.

Counts the number of calls to deallocateAll.

Chooses all numXxx flags.

Tracks bytes currently allocated by this allocator. This number goes up and down as memory is allocated and deallocated, and is zero if the allocator currently has no active allocation.

Tracks total cumulative bytes allocated by means of allocate, expand, and reallocate (when resulting in an expansion). This number always grows and indicates allocation traffic. To compute bytes deallocated cumulatively, subtract bytesUsed from bytesAllocated.

Tracks the sum of all delta values in calls of the form expand(b, delta) that succeed (return true).

Tracks the sum of all b.length - s with b.length > s in calls of the form realloc(b, s) that succeed (return true). In per-call statistics, also unambiguously counts the bytes deallocated with deallocate.

Tracks the sum of all bytes moved as a result of calls to realloc that were unable to reallocate in place. A large number (relative to bytesAllocated) indicates that the application should use larger preallocations.

Tracks the sum of all bytes NOT moved as result of calls to realloc that managed to reallocate in place. A large number (relative to bytesAllocated) indicates that the application is expansion-intensive and is saving a good amount of moves. However, if this number is relatively small and bytesSlack is high, it means the application is overallocating for little benefit.

Measures the sum of extra bytes allocated beyond the bytes requested, i.e. the internal fragmentation. This is the current effective number of slack bytes, and it goes up and down with time.

Measures the maximum bytes allocated over the time. This is useful for dimensioning allocators.

Chooses all byteXxx flags.

Combines all flags above.