As of December 2020, Google Chrome accounted for about 66 percent of the global desktop internet browser market share. The reliable and feature-packed web browser also dominates the mobile internet browser market.

Sadly, Google Chrome is a resource-intensive web browser. The browser is known to consume a noticeable amount of RAM for its proper functioning. According to a new report from Windows Latest, Google might soon resolve the performance issues associated with Chrome.

So here’s everything that you need to know about the upcoming Google Chrome update.

ALSO READ: 10 Best Google Chrome Alternatives


PartitionAlloc-Everywhere Support For Google Chrome

Recently, ‘PartitionAlloc-everywhere’ support has been spotted in Chrome’s source code. Google started working on the aforementioned feature back in 2020 and it’s now available in the latest beta version of Chrome for Windows 10 and Android.

PartitionAlloc-Everywhere Support For Google Chrome

The three primary benefits of ‘PartitionAlloc-everywhere’ support are faster browser opening, improved speed while loading internal pages, and better resource management in other words lesser RAM usage.

PartitionAlloc is also available for Linux but at the time of writing this article, it’s plagued with issues.

A Google engineer noted in a Chromium bug post, “Switch to PartitionAlloc on Linux. This is already the default on Windows and Android and has been shipping to the beta on both platforms. Nevertheless, issues may remain on Linux.

RELATED: YouTuber Opened 6000 Chrome Tabs On The Mac Pro

To further reduce RAM usage, Google has conducted another experiment. The conclusion drawn from this experiment was that merging the regular and aligned partitions could reduce memory usage.

Google further explained that,

Having two separate partitions is required when the regular one doesn’t provide the desired alignment. Without that, it’s beneficial performance and memory-wise to have a single partition. Performance is better since aligned allocations (which are actually plentiful in Chromium) can leverage the thread cache. Memory footprint improves from lower fragmentation, and not paying the fixed cost of partition metadata.

If everything goes well we can soon expect to see PartitionAlloc-everywhere in the stable version of Chrome.