1 .\" Copyright (c) 1993 by Thomas Koenig (ig25@rz.uni-karlsruhe.de)
3 .\" %%%LICENSE_START(VERBATIM)
4 .\" Permission is granted to make and distribute verbatim copies of this
5 .\" manual provided the copyright notice and this permission notice are
6 .\" preserved on all copies.
8 .\" Permission is granted to copy and distribute modified versions of this
9 .\" manual under the conditions for verbatim copying, provided that the
10 .\" entire resulting derived work is distributed under the terms of a
11 .\" permission notice identical to this one.
13 .\" Since the Linux kernel and libraries are constantly changing, this
14 .\" manual page may be incorrect or out-of-date. The author(s) assume no
15 .\" responsibility for errors or omissions, or for damages resulting from
16 .\" the use of the information contained herein. The author(s) may not
17 .\" have taken the same level of care in the production of this manual,
18 .\" which is licensed free of charge, as they might when working
21 .\" Formatted or processed versions of this manual, if unaccompanied by
22 .\" the source, must acknowledge the copyright and authors of this work.
25 .\" Modified Sat Jul 24 19:00:59 1993 by Rik Faith (faith@cs.unc.edu)
26 .\" Clarification concerning realloc, iwj10@cus.cam.ac.uk (Ian Jackson), 950701
27 .\" Documented MALLOC_CHECK_, Wolfram Gloger (wmglo@dent.med.uni-muenchen.de)
28 .\" 2007-09-15 mtk: added notes on malloc()'s use of sbrk() and mmap().
30 .\" FIXME . Review http://austingroupbugs.net/view.php?id=374
31 .\" to see what changes are required on this page.
33 .TH MALLOC 3 2017-07-13 "GNU" "Linux Programmer's Manual"
35 malloc, free, calloc, realloc \- allocate and free dynamic memory
38 .B #include <stdlib.h>
40 .BI "void *malloc(size_t " "size" );
41 .BI "void free(void " "*ptr" );
42 .BI "void *calloc(size_t " "nmemb" ", size_t " "size" );
43 .BI "void *realloc(void " "*ptr" ", size_t " "size" );
44 .BI "void *reallocarray(void " "*ptr" ", size_t " nmemb ", size_t " "size" );
48 Feature Test Macro Requirements for glibc (see
49 .BR feature_test_macros (7)):
65 bytes and returns a pointer to the allocated memory.
66 .IR "The memory is not initialized" .
73 or a unique pointer value that can later be successfully passed to
78 function frees the memory space pointed to by
80 which must have been returned by a previous call to
87 has already been called before, undefined behavior occurs.
90 is NULL, no operation is performed.
94 function allocates memory for an array of
98 bytes each and returns a pointer to the allocated memory.
99 The memory is set to zero.
108 or a unique pointer value that can later be successfully passed to
113 function changes the size of the memory block pointed to by
118 The contents will be unchanged in the range from the start of the region
119 up to the minimum of the old and new sizes.
120 If the new size is larger than the old size, the added memory will
125 is NULL, then the call is equivalent to
134 is not NULL, then the call is equivalent to
138 is NULL, it must have been returned by an earlier call to
143 If the area pointed to was moved, a
149 function changes the size of the memory block pointed to by
151 to be large enough for an array of
153 elements, each of which is
156 It is equivalent to the call
159 realloc(ptr, nmemb * size);
166 fails safely in the case where the multiplication would overflow.
167 If such an overflow occurs,
173 and leaves the original block of memory unchanged.
179 functions return a pointer to the allocated memory,
180 which is suitably aligned for any built-in type.
181 On error, these functions return NULL.
182 NULL may also be returned by a successful call to
187 or by a successful call to
197 function returns no value.
201 function returns a pointer to the newly allocated memory, which is suitably
202 aligned for any built-in type and may be different from
204 or NULL if the request fails.
207 was equal to 0, either NULL or a pointer suitable to be passed to
212 fails, the original block is left untouched; it is not freed or moved.
216 function returns a pointer to the newly allocated memory.
218 it returns NULL and the original block of memory is left untouched.
225 can fail with the following error:
229 Possibly, the application hit the
236 For an explanation of the terms used in this section, see
242 Interface Attribute Value
249 T} Thread safety MT-Safe
256 POSIX.1-2001, POSIX.1-2008, C89, C99.
259 is a nonstandard extension that first appeared in OpenBSD 5.6 and FreeBSD 11.0.
261 By default, Linux follows an optimistic memory allocation strategy.
264 returns non-NULL there is no guarantee that the memory really
266 In case it turns out that the system is out of memory,
267 one or more processes will be killed by the OOM killer.
268 For more information, see the description of
269 .IR /proc/sys/vm/overcommit_memory
271 .IR /proc/sys/vm/oom_adj
274 and the Linux kernel source file
275 .IR Documentation/vm/overcommit-accounting .
279 allocates memory from the heap, and adjusts the size of the heap
282 When allocating blocks of memory larger than
286 implementation allocates the memory as a private anonymous mapping using
289 is 128\ kB by default, but is adjustable using
291 Allocations performed using
293 are unaffected by the
295 resource limit only prior to Linux kernel 4.7 (see
298 To avoid corruption in multithreaded applications,
299 mutexes are used internally to protect the memory-management
300 data structures employed by these functions.
301 In a multithreaded application in which threads simultaneously
302 allocate and free memory,
303 there could be contention for these mutexes.
304 To scalably handle memory allocation in multithreaded applications,
305 glibc creates additional
306 .IR "memory allocation arenas"
307 if mutex contention is detected.
308 Each arena is a large region of memory that is internally allocated
314 and managed with its own mutexes.
326 Glibc assumes that this is done
327 (and the glibc versions of these routines do this); if you
328 use a private malloc implementation that does not set
330 then certain library routines may fail without having
340 are almost always related to heap corruption, such as overflowing
341 an allocated chunk or freeing the same pointer twice.
345 implementation is tunable via environment variables; see
349 .\" http://g.oswego.edu/dl/html/malloc.html
350 .\" A Memory Allocator - by Doug Lea
352 .\" http://www.bozemanpass.com/info/linux/malloc/Linux_Heap_Contention.html
353 .\" Linux Heap, Contention in free() - David Boreham
355 .\" http://www.citi.umich.edu/projects/linux-scalability/reports/malloc.html
356 .\" malloc() Performance in a Multithreaded Linux Environment -
357 .\" Check Lever, David Boreham
364 .BR malloc_get_state (3),
367 .BR malloc_usable_size (3),
371 .BR posix_memalign (3)