The problem of unexpected hang when closing Chrome browser is solved!

This week, Google announced a series of improvements to the Chrome browser.

• Optimize the speed of the multi-function search box (according to the Google experiment found that the search results 4 times may be displayed within 500 milliseconds)
• Chrome browser performance optimization in Chrome OS (in addition to the 20% browser process memory reduction, the M93 field data in Chrome OS also shows that the total memory occupancy is reduced by 15%, which improves the single and multi-tab Chromebook browsing experience)
• Delete Chrome's memory history local cache mechanism (completely solve the problem of unexpected hang when shutting down)

At first, Google cached the memory usage history locally in the Chrome browser in order to make Chrome start faster. However, through the investigation and analysis of the actual application, it is found that this kind of memory history caching will not only increase code complexity and unnecessary memory usage, but also cause the browser to hang when it is closed.

The reason is: when Chrome is closing the page or browser, on some operating systems (typically Windows 7), when the memory is occupied by other applications, the background priority thread may lack I/O for a long time, resulting in The closed page or browser is just suspended, not really closing the process. Over time, these Chrome processes will accumulate and consume all of the device's memory, causing Chrome apps to stop responding, crash, and freeze. If you are using Chrome OS or Windows, you may even be unable to shut down, stuck on the shutdown page for a long time and wait for the Chrome process to end.

Therefore, the local cache of memory usage history brings poor performance experience to users, which is also an important reason why Google chooses to delete the memory history cache.