From selivanov.dmitriy at gmail.com  Thu Jun 22 09:12:15 2017
From: selivanov.dmitriy at gmail.com (Dmitriy Selivanov)
Date: Thu, 22 Jun 2017 11:12:15 +0400
Subject: [Rd] Issue with memory deallocation/fragmentation on systems
	which use glibc
Message-ID: <CAJdZCv1acw4A1VOHgT7DWO3hp5XqLmwt5kmFHq6Kq-bQ8DGhXg@mail.gmail.com>

A few additional details. According to Linux Programmer's Manual

   1. http://man7.org/linux/man-pages/man3/mallopt.3.html
   2. http://man7.org/linux/man-pages/man3/malloc_trim.3.html

And if I understood everything correctly `free` could trigger `malloc_trim`
based on value of several environment variables - MALLOC_TOP_PAD_ and
MALLOC_TRIM_THRESHOLD_. However setting them as low as 1 or 0 doesn't have
any effect (but as I wrote in previous email manual call of `malloc_trim`
helps to release memory).

	[[alternative HTML version deleted]]



[Rd] Issue with memory deallocation/fragmentation on systems which use glibc
Dmitriy Selivanov