docs/Writerside/topics/memory.md

Sun, 09 Feb 2025 22:02:13 +0100

author
Mike Becker <universe@uap-core.de>
date
Sun, 09 Feb 2025 22:02:13 +0100
branch
docs/3.1
changeset 1173
99fc65d2d22b
parent 1170
49cc0bbea6a9
permissions
-rw-r--r--

add sub-section intro texts to install.md

relates to #451

# Memory Management

With the `CxAllocator` interface UCX provides the possibility to use custom allocator functions for different purposes.
Many UCX functions support the use of specialized allocators or provide a second function suffixed with `_a`.

For convenience, functions that are not explicitly requesting an allocator - like e.g. `cx_strdup_a()` - also accept
`NULL` as an allocator, in which case the `cxDefaultAllocator` and stdlib functions are used.

Additionally, UCX also provides a [memory pool](mempool.h.md) implementation of the allocator interface.

> Although not part of the public API, UCX is also implementing the allocator interface
> in its own test suite: `CxTestingAllocator`. This allocator keeps track of memory allocations
> and de-allocations with the goal to detect memory management errors.  

mercurial