Google's Chrome team is looking at heap scanning to reduce memory-related security flaws in Chrome's C++ codebase, but the technique creates a toll on memory – except when newer Arm hardware is used.

We have some programs at work that are using a lot of memory (1-2 GBs) and we'd like to trim that down. This isn't a memory leak issue - the memory use doesn't increase over time, but rather an issue ...