Desperate users have been complaining about it for years, countless memes make fun of it – the memory requirements of Google’s Chrome browser are almost legendary. But now this should end and Chrome finally need less RAM. The key to the much-needed improvement is a Windows 10 API.
With the “TerminateProcess” interface, Google wants to ensure that all system processes that are used by the Chrome browser are actually terminated and that the reserved memory is released when the corresponding tab is closed. On the Chromium side explains Google that they have been working towards the integration of TerminateProcess for a long time.
Not Google’s first attempt
It’s not the first time that Google’s developers have decided to put Chrome on the RAM diet. Only this summer, Google announced that it wanted to save around a quarter of the RAM. The SegmentHeap used at the time was unsuccessful under Windows, on the contrary: Chrome’s stability suffered, which is why the experiment was aborted, like MSPowerUser reports.
At the beginning of the month, Google initially devoted itself to more important things in terms of Chrome, namely the security patches. Eight security holes could be closed with the version 87.0.420.88. Before the patch, attackers were able to trigger memory errors in Chrome and thus smuggle in malicious code.
One of the advantages of Chrome is the flexibility provided by plugins and extensions. They do not make the browser faster or reduce the need for resources, but they do bring many new possibilities. However, security should always be considered, because not all of these extensions are really waterproof.