{"id":168709,"date":"2026-04-14T17:12:49","date_gmt":"2026-04-14T15:12:49","guid":{"rendered":"https:\/\/prohoster.info\/blog\/novosti-interneta\/dostupna-biblioteka-upravleniya-pamyatyu-jemalloc-5-3-1"},"modified":"2026-04-14T17:12:49","modified_gmt":"2026-04-14T15:12:49","slug":"dostupna-biblioteka-upravleniya-pamyatyu-jemalloc-5-3-1","status":"publish","type":"post","link":"https:\/\/prohoster.info\/en\/blog\/news\/dostupna-biblioteka-upravleniya-pamyatyu-jemalloc-5-3-1","title":{"rendered":"The jemalloc memory management library version 5.3.1 is now available.","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"
Four years after the last update, the release of the jemalloc memory management library version 5.3.1 is now available, offering an alternative implementation of malloc functions optimized for reducing fragmentation and working on multiprocessor systems. To address lock issues on multicore systems, jemalloc uses an isolated memory allocation area for each CPU core, allowing for linear scalability as the number of threads increases. <\/p>\n
In June 2025, the project author stopped maintenance and archived the jemalloc repository. However, a month ago, Meta, which uses jemalloc in its infrastructure, resumed development. The library was originally developed for FreeBSD and has been the default in that OS since 2005. The library's code is written in C and is distributed under the BSD license. <\/p>\n
Among the changes: <\/p>\n
\n
The pvalloc function has been implemented, which may be useful for replacing the libc memory allocator.\n
In debug builds, a mode for detecting double calls to the free() function has been enabled. A parameter, debug_double_free_max_scan, has been added to configure the size of the stack for scanning.\n
An assembly option «—enable-pageid» has been added to set tags when mapping memory using prctl with the PR_SET_VMA flag. Once enabled, the mapping can be tracked through \/proc\/\/maps.\n
The parameter «prof_bt_max» has been added to allow setting the maximum stack depth for profiling.\n
An assembly option «—enable-force-getenv» has been introduced to use the standard getenv() function instead of the protected secure_getenv().\n
An assembly option «—disable-dss» has been added to disable the use of the sbrk() function.\n
The parameter «tcache_ncached_max» has been added to limit the number of elements in the thread cache.\n
The parameter «calloc_madvise_threshold» has been introduced to configure the use of the kernel madvise mechanism or the memset function for zeroing memory allocated via calloc.\n
An assembly option «—disable-user-config» has been added to disable loading settings from the \/etc\/malloc.conf file or the MALLOC_CONF environment variable.\n
The parameter «process_madvise_max_batch» has been introduced to limit the number of memory blocks for each madvise batch operation.\n
The parameter «disable_large_size_classes» has been added to disable the new algorithm for calculating the allocated memory size, reducing overhead when allocating blocks larger than 4 pages of memory.\n
The mallctl utility has gained options: opt.prof_bt_max, arena..name, thread.tcache.max, thread.tcache.ncached_max.write, thread.tcache.ncached_max.read_sizeclass, arenas.hugepage, and approximate_stats.active. <\/ul>\n