Google Chrome 72 hit by a pair of oddly ironic bugs



[ad_1]

Google Chrome 72 hit by a pair of oddly ironic bugs

Chrome bugbuster at work

GOOGLE LEADERS IN THE MARKET Web browser, Chrome has suffered a significant tonnage after an "experiment" in the latest version.

Users who have Network Service Experimentation enabled in Chrome 72 find that some extensions do not work, no longer respond to their queries, and block notifications after opening a tab.

It's a server-side subscription to a small subset of users, which means you have no idea what we're talking about or are holding your laptop in your arms, crying softly and saying " thank you…. Someone understands my pain. ".

Google stated that the problems only affected 0.01% of its user base, and that it would not go back, pointing out that it usually did this kind of thing without any problem and that nobody would find out .

The good news is that there is a "Network Service Experience" indicator in the Chrome Flags menu. By disabling it, you will find that everything is beautiful again.

One of the biggest ironies (first part) is that this has serious repercussions on ad blockers, which are already threatened by the planned browser changes in a future release.

Another separate bug, but just as strange, is that the construction causes even more than the monopoly of the processor. Not serious, right? It becomes … uh … ironic (second part). Verifying CPU usage in Chrome's task manager is in itself a problem on some computers, including the Pixelbook, Pixel Slate and many others.

This amount of CPU resources can seriously slow down your day and maximize the CPU completely, which means shifts, crashes and bad vibrations in general.

Google seems to control this one in that it no longer looks for examples of the problem in nature, which usually indicates that the cause of the problem has been identified and that the fix is ​​under development.

It is not certain that there are really processor spikes outside the task manager. Google does not know if there are other forces at work or is simply a bug related to surveillance.

In the meantime, it is advisable not to prick your processor when the task manager is open. well, do not open the task manager, of course.

Chrome Unboxed, the first to have spotted the story, hinted that there was a correlation between the devices involved and the deployment of the Android 9.0 Pie subsystem and that disabling the Play Store was a solution to the problem. decent bypass. μ

Further reading

[ad_2]

Source link