Google Chrome. The biggest problem that Google's browser has at the moment is the very high consumption of RAM memory, many users are complaining about this problem. Those at Google also know about its existence, so they decided to work on a solution that would make Google Chrome easier to use for everyone, and it could be offered publicly in the not too distant future.
Google Chrome. According to some information discovered inside the source code of the browser, those from Google intend to reduce to a good extent the consumption of RAM by blocking some functions until the browser is closed. These include deleting caches from Google Chrome, reporting usage information to Google, writing information to the HDDs on which the browser is installed, plus other functions of this kind, which consume a lot of RAM memory.
Google Chrome will finally solve the problem of RAM memory consumption
Google Chrome. All these things will only be done when the browser is effectively closed by the user, so that in the meantime the rest of the functions will work much better, and with less RAM memory consumption. Best Effort Tasks is the name of the function that Google Chrome will have implemented, and in general, the main functionality will have priority when running and loading in RAM, in relation to the functions that are less important for the user.
The new flag can be switched on and off on "chrome://flags". It is disabled by default, and if turned on, all tasks of lowest priority "base::TaskPriority::BEST_EFFORT" will not be executed. This is equivalent to the command line flag "–disable-best-effort-tasks". With this flag on, tasks of the lowest priority will not be executed until shutdown. The queue of low priority tasks can increase memory usage. Also, while it should be possible to use Chrome almost normally with this flag, it is expected that some non-visible operations such as writing user data to disk, cleaning caches, reporting metrics or updating components won't be performed until shutdown.
Google Chrome. Tasks that have low priority will be blocked until closed, but it is not clear how much RAM memory this change would save, considering that a lot is consumed. At the moment, users of Google Chrome in the alpha version have the possibility to search for the flag best effort Tasks to activate this functionality, but there is a possibility that it is not 100% functional, considering that it is still being tested.
