about.md- allocator.h.md
- array_list.h.md
- buffer.h.md
- collection.h.md
- collections.md
- compare.h.md
- features.md
- hash_key.h.md
- hash_map.h.md
- install.md
- iterator.h.md
- json.h.md
- kv_list.h.md
- license.md
- linked_list.h.md
- list.h.md
- map.h.md
- memory.md
- mempool.h.md
- parsers.md
- printf.h.md
- properties.h.md
- streams.h.md
- string.h.md
- strings.md
- test.h.md
- tree.h.md
- utils.md
1 # Memory Management
2
3 With the `CxAllocator` interface UCX provides the possibility to use custom allocator functions for different purposes.
4 Many UCX functions support the use of specialized allocators or provide a second function suffixed with `_a`.
5
6 For convenience, functions that are not explicitly requesting an allocator - like e.g. `cx_strdup_a()` - also accept
7 `NULL` as an allocator, in which case the [default allocator](allocator.h.md#default-allocator) is used.
8
9 Additionally, UCX also provides a [memory pool](mempool.h.md) implementation of the allocator interface.
10
11 > Although not part of the public API, UCX is also implementing the allocator interface
12 > in its own test suite: `CxTestingAllocator`. This allocator keeps track of memory allocations
13 > and deallocations with the goal to detect memory management errors.
14