Although Google Chrome is the browser most chosen by users, and both the Google engineering team and the various Chromium participants are working hard to improve its performance and functions, there are still some points that can be quite a room for improvement.
And no, for a change I am not going to talk about memory management, the great black hole of Google’s browser, and in which they continue to work but have not yet achieved the results that we all hope.
On this occasion I am talking about another problem: its integration with the various security solutions (antivirus, suites, etc.) existing on the market and that users use to protect themselves from the huge volume of threats that are activated at the same time that we turn on the PC and it connects to the Internet.
Threats that can turn our system into a bot at the service of cybercriminals, steal our data to try to extort us, take over our credit card to empty our checking account… A universe of threats that we must be prepared for.
The problem with Google Chrome in this regard is that, although some antivirus manufacturers have gone to great lengths to improve their integration with the browser, many processes are substantially slowed down when they must be monitored by security software.
From accessing a web page to downloading a file, there are many operations that are supervised by this software, and the way in which Windows and Google Chrome manage these processes translates into pauses that slow down the processes.
The good news, as we can read on the Chromium development page, is that those responsible for Google Chrome already know what is the cause of this problem and, therefore, has already proposed a solution.
This is what we can read on the development page: «Anti-virus programs and other scanners may briefly lock new files which can lead to frequent problems with saving bookmarks and other files that use the ImportantFileWriter. The race condition between closing the temporary file and moving it gets hit on a regular basis on some system«.
The proposed solution, which is only necessary for Windows, as this is where this problem occurs, involves modifying the behavior of the browser in downloads and other disk accesses for file writing and modification operations.
With this change, the volume of operations supervised by the operating system (not by the antivirus) generated by said “micro-cuts” would be reduced and, therefore, when carrying out these actions with Google Chrome (and, of course, the rest Chromium-based browsers), the processes would be perceptually faster, as those small but annoying interruptions would not occur.