Date: Tue, 05 Feb 2019 11:45:29 -0100
From: René Kuligowski<renekuligowski@o2mail.de>
I also checked thoroughly in the VFSes (/sys, /proc etc.) and ran a
mem tracer. The memory blocks are not freed, but stay allocated, like
from a forgotten free() call or a severely buggy malloc() call (like the
common issues with gcc 3.3 and 4.5).
Can you see which software module "owns" the memory that is not freed?
Could it be, for instance, that Emacs loaded some system shared
libraries, and the OS didn't unload them?