Google Chrome is the most popular web browser in the world today, and for all its advantages, it has its major drawbacks: Google Chrome takes up a lot of system RAM. Earlier in June 2020, a report announced that Google plans to use Microsoft Segment Heap technology to reduce chrome-occupied RAM by one-third. Google started the process of using Segment Heap; But this technology caused some instability in Chrome; For this reason, the company from Mountain View finally decided to leave Segment Heap.
Excessive RAM consumption is very annoying for users of this browser and makes working with Chrome on old systems tedious. The more tabs you open, the slower Chrome will be and it will negatively affect your browsing experience. Eventually, you may end up slowing down the system and shutting down the tabs; But after closing the tabs, continue to see the RAM memory occupied. Google seems to be trying to fix this.
Recently, the developers of Google Chrome intend to use one of the Windows 10 APIs called Use TerminateProcess to completely shut down browser processes. This feature makes the processes in question and all related crunches inaccessible, regardless of the circumstances and subsequent consequences.
In fact, Google says TerminateProcess helps users recover used Chrome memory much faster and better. According to Google, it is difficult, costly, and slow to completely close a particular processing process, and because of the complexity of the software, it is impossible to Race Condition Prevented. In recent times, Google has gradually shifted to TerminateProcess for a variety of processes.
Turning off tabs or shutting down the Chrome browser altogether while the system is slowing down may not free up RAM as quickly. However, using TerminateProcess will probably eliminate this type of Chrome behavior and reduce the number of browser crashes.
TerminateProcess is a feature of the Windows operating system, which means that the efforts of Google developers are only for the version of Windows 10 Chrome. We do not know exactly when the new Chrome update will be released to address this issue, and Google has not announced a specific date.