Technology

Google: Chrome Browser Memory Eating Problem Is Not Solved Yet

Google has decided to disable a new solution to reduce memory requirements in Chrome on Windows 10. The feature was originally developed by Microsoft for its own Edge browser.

The negative headlines around Google’s widespread Chrome browser never stop. The program has long been considered a resource eater and can have a blatant influence on both system and battery performance. Microsoft had recently tackled one of the main problems, namely the enormous need for RAM. The Redmond Company provided an innovation for Windows 10 that should help all browsers based on the Chromium open-source project – including Chrome in this area.

New storage management works, but creates problems

The solution presented by Microsoft in mid-June uses a new segmented data structure for the memory management of Win32 programs, which was introduced with the May 2020 update (version 2004) for Windows 10. As a result, official information according to the RAM requirements of the Edge browser could be reduced by 27 percent.

Google initially decided to also use this innovation for its own Chrome browser. However, an Intel engineer uncovered worrying sequelae to this implementation earlier this month.

RAM optimization not completely deleted

As first noticed by Intel and then confirmed by Google, the changed memory management of Chrome under Windows 10 leads to a considerable deterioration in the performance of PCs. With browser tests such as Speedometer 2.0, WebXPRT3, and JetStream2, CPU performance was reduced by up to 10 percent and the processor’s energy consumption increased by up to 13 percent. Google programmer Bruce Dawson described the cost of CPU performance as “too high” to continue using this form of optimization in the browser. Based on these findings, Google will deactivate the new RAM management under Windows 10 with the upcoming Chrome version 85. However, improvements in the area should continue to be worked on. According to Dawson, the current measure is just a short delay for more efficient storage management under Chrome. How exactly this should then be implemented remains unclear for the time being.

For frustrated Chrome users, there is also the opportunity to look for an alternative. As recently pointed out, offer browser as just Microsoft’s new Edge or for Mac users Apple’s Safari in terms of speed and energy efficiency advantages over Chrome.

Recent Posts

Google Health: A bug is currently really annoying Pixel Watch users

An annoying software error is currently plaguing many owners of the Google Pixel Watch. The…

20 hours ago

Pixel Watch 5: Leak shows the design of the new Google smartwatch in advance

After the new Google smartphones in the Pixel 11 series, official marketing images of the…

20 hours ago

Epson is in court: first lawsuit over planned obsolescence

A French consumer protection association is taking Epson to court. The accusation is of planned…

20 hours ago

EU brings Meta to its knees: ChatGPT is running again in WhatsApp chat

After a months-long exclusion by the Facebook group Meta, the well-known AI chatbot ChatGPT has…

20 hours ago

Good news for Windows 11: Microsoft is banning advertising from search

Microsoft is fundamentally redesigning the search in Windows 11. The operating system loses advertising, forced…

21 hours ago

iOS 27 public beta is here: Apple starts the test phase for all iPhone users

Interested users can now install the first public beta version of iOS 27 on their…

21 hours ago