Antique Tractors Forum banner

1 - 1 of 1 Posts

·
Banned
Joined
·
1 Posts
Discussion Starter #1
What to do if Chrome's CPU is 100% busy visiting a web page: what does it depend on and how to solve the problem.

Several users have reported that using the new Chrome 66 ( Chrome download of the latest version and new features of release 66 ), the use of the processor has begun to jump to levels never seen before, visiting many web pages.

21539


We, too, have encountered the problem that seems to be directly related to introducing the Site isolation feature in Chrome.

The so-called same-origin policy, an approach used in all web browsers, provides that any web page must never access the content of other pages simultaneously open and spy on the data managed in other tabs or other browser processes, password manager included.

Some bugs in the browser, in the operating system, or at the hardware level (think of the Specter vulnerability discovered in the processors) can complicate things and make it possible, by malicious code, to overcome the security measures provided by the same-origin policy.

The Site isolation feature introduced in Chrome with the release of version 66 of the browser introduces an additional level of security, thus mitigating the known Specter flaw ( Check if the processor in use is vulnerable to Meltdown and Specter ) and bugs (even those currently unknown) possibly present at various levels.

Site isolation means that pages from different websites are always loaded into different processes, each within its sandbox, to limit the "freedom of action.

This is certainly an effective approach, but it has some disadvantages: Chrome uses more memory (about 10-12% more with different tabs open). However, it seems that the impact on the CPU is also far from negligible: after installing Chrome 66 or, in any case, updated to this latest version of the Google browser, many users have begun to report processor usage, often close to 100%.

To solve the problem, while waiting for the Google technicians to further optimize the Site isolation functionality, you can apply the following steps:

- Type chrome: // flags / # site-isolation-trial-opt-out in the address bar.

- Choose Opt-out from the corresponding menu, then consent to the complete restart of Chrome.

In this way, the problem related to the 100% CPU usage in Chrome should be solved even if the advice - after the next updates - is to reactivate the feature (which has obvious benefits in terms of security).

Recall that to check which Chrome processes or tabs are more CPU intensive, just press the SHIFT + ESC key combination, then click on the CPU column so that the elements that occupy the processor the most are shown first.

Another process that often blocks the CPU usage at 100% is Software Reporter Tool: in the article How to block the Software Reporter Tool process, we have seen how to solve the problem.
 
1 - 1 of 1 Posts
Top