SegmentHeap does not finish making crumbs with Chrome

My joy in a well. Well mine and others many people who had pinned their hopes on SegmentHeap. If you are a user of Google Chrome in Windows 10 it is quite likely that you know what I am talking about. Otherwise you should know that a little less than a month ago we already told you about this novelty that has arrived with Windows 10 2004, and that it promised to be a solution (or at least a partial solution) to the tremendous problem that, for a long time , it has Google Chrome with RAM memory consumption.

For making a quick summary of the reason that SegmentHeap appeared to be the blackbird of May Update 2020We must remember that this is an improvement in the method used by the system and the applications to manage the heaps (mounds) in the data structure, as well as in the dynamic allocation of memory. The problem of Chrome, and of many other applications that act in a similar way, is that the provisioning of resources causes, with the classic method, now called LegacyHeap, an excessive consumption of resources, which on many occasions is above real needs. thereof.

The developers of Google Chrome, upon learning of the introduction of SegmentHeap in the latest Windows update, chose to incorporate it into the browser manifest. Something logical, since some initial tests on the matter resulted in a memory consumption reduction of up to 27%. The implementation, however, could not be immediate, as they produced some problems trying to compile Chrome with the Windows SDK. However, it was finally possible in a beta of Chrome V85.

And so far the happy part of the story, because after doing some tests with Chrome V85, its developers have decided to go back and remove SegmentHeap from the application manifest, since they claim it causes some problems related to system performance. And so they have returned to LegacyHeap, which will continue to be the mound management method employed by Google’s browser. According to Chrome engineers, performance losses were measured with WebXPRT3, Speedometer2 and JetStream2, three benchmarks in their field.

Microsoft’s response has been to affirm that with the use of SegmentHeap it is true that it can increase the use of the CPU, but that this increase is compensated by the decrease, according to them more pronounced, in the memory consumption. They also affirm that this transaction is usually carried out in reverse, that is, that many applications tend to reduce CPU consumption, giving more use of RAM. The Microsoft engineer who responds to the Google one argues that the Chrome problem is due to a bug and that some improvements can be made to reduce the impact on processor consumption.

Despite the Microsoft engineer’s response, the Chrome development team has chosen to forgo SegmentHeap for now. That is, yes, the good news. And is that the Google browser development team has not definitively ruled out its use, but it has been considered to continue conducting tests in the future, to see if at some point it is possible to adopt it.

With information from MSPoweruser

Leave a Reply

Your email address will not be published. Required fields are marked *