Hardened Malloc Light
Hardened Malloc is a hardened memory allocator which can be used with many applications to increase security.
According to the author's GitHub description: 
This is a security-focused general purpose memory allocator providing the malloc API along with various extensions. It provides substantial hardening against heap corruption vulnerabilities. The security-focused design also leads to much less metadata overhead and memory waste from fragmentation than a more traditional allocator design. It aims to provide decent overall performance with a focus on long-term performance and memory usage rather than allocator micro-benchmarks. It offers scalability via a configurable number of entirely independently arenas, with the internal locking within arenas further divided up per size class.
The development goal of Hardened Malloc Light is pre-installation by default.
Hardened Malloc Light uses different compile time options.
- Hardened Malloc (compile time options as close to original upstream as possible)
- Hardened Malloc Light (compile time option
VARIANT=lightas provided by upstream)
Both, Hardened Malloc and Hardened Malloc Light are already installed by default but not yet enabled by default.
Hardened Malloc Light is not yet enabled by default since there are still various known issues. Most notably, it breaks possibly VirtualBox host software crashes, which haven't been reproduced by testers yet.
Advanced users may still wish to use Hardened Malloc for specific high risk applications.
Before getting started with Hardened Malloc (Light) it is recommended to first test the host operating system using
memtest86+ (link) since hardware issues with RAM might be more likely be resulting in system crashes with Hardened Malloc (Light) enabled. 
Forum development discussion:
hardened-malloc-light-enable  is provided as an easy way to enable Hardened Malloc Light globally.
Hardened Malloc Light can be disabled either per application or globally.
Disable per Application
Apply the following steps to disable Hardened Malloc Light per application.
chromium with the actual application which should be started without ld system preload.
Apply the following steps to globally disable Hardened Malloc Light.
If the system is still fully functional, the easiest way is to uninstall the
sudo apt purge hardened-malloc-light-enable
1) Boot into recovery mode. Optional.
This is only required if the system is no longer bootable. In this case, refer to boot into recovery mode.
2) View the
If not using
/etc/ld.so.preload for anything else. Warning: this removes all entries from
sudo rm /etc/ld.so.preload
slowdown by swap-file-creator shutdown
- related to above cryptsetup slowdown by factor ~ 7
- workaround OK https://github.com/Whonix/swap-file-creator/commit/c65edf17f952ac4a296ae6a0aac5a10541579ff6
- chromium from flathub also functional (Hardened Malloc Light is probably disregarded inside flatpak's bubblewrap based sandbox?)
no workaround available
- cryptsetup slowdown by factor ~ 6
- might break Kicksecure ™ build process
- TODO: test building Kicksecure ™ with Hardened Malloc Light enabled
- chromium crashes with Hardened Malloc (Light) (requires disabling using
- reported upstream: https://bugs.debian.org/971876
- VirtualBox crashes with hardened memory allocator Hardened Malloc on the host 
- Installing Hardened Malloc and enforce enabling it will lead to duplication in Copy to VM & Move to VM
- glibc feature request: LD_ETC_IGNORE - environment variable to ignore /etc/ld.so.preload configuration file on a per-application basis
Credits and Source Code
The original source software is maintained by security researcher, Daniel Micay.
This website is the software fork homepage for Hardened Malloc Light, with a focus on pre-installation by default in Whonix ™ and Kicksecure ™. The software fork source code can be found here. Continuous integration: travis CI
In the experience of Kicksecure ™ developer Patrick, the VirtualBox host software crashed with Hardened Malloc enabled with different error messages when faulty RAM banks where used compared to VirtualBox host software crashes with RAM banks that did not show any errors in