Google and Microsoft Teamed Up To Fix Chrome’s Heavy RAM Usage

Even though Many people laud chrome, the extreme impact it has on the RAM is merely cataclysmic. Whether many gigabytes or Sodium DDR4, Google’s Chrome is eating out any kind of memory that it encounters. There are, evidently, those expensive PCs that live through the effects of the browser but we are mentioning the regular, day to day users.

The problem is that Chrome is exceptionally advanced for this time. People might disagree, but the things Chrome offers which impress us is devouring memory. For example, image search: all the images are already loaded as you scroll utilizing a keyword, and as you search through them which is not an important matter at all. That because you don’t have to wait for them to appear; all this data is pre-loaded into the browser’s memory even if it amazes us or not, and thus puts some pressure on it.

Google and Microsoft partnered to sort out the heavy RAM usage in Chrome

However, this problem is mainly observable on lower-end computers. The lag occurring even when one opens the Google Chrome browser on slower computers is because of the ImagePreReader which pre-reads Chrome DLL, states an article by Windows Latest. This means that there is a tiny file which is opened by a subprogram, and on a slower computer, the process takes a bit longer than usual (approximately 1.33 seconds, stated the article).

To resolve this issue, Microsoft has been partnering with Google with the principal target being to solve the primary startup lag created by the Chrome DLL. A Microsoft engineer talks about this issue on a forum and shares their suggested fix for it.

The solution, even if it is still being developed, has been created by that engineer. Both Microsoft and Google believe that as soon as the issue is solved, CPU and RAM usage for Google Chrome will also be reduced. Even though this is only theoretical, it would actually be nice that Chrome may be memory effective.

Be the first to comment

Leave a Reply

Your email address will not be published.