[QUOTE=garo;380127]A recent update of chrome caused this problem for me too.[/QUOTE]

I have some reservations about the silent upgrade techniques of Chrome.
Imagine if one were just about to place a bid in the last moments of an auction when an upgrade commences.
Instead of having an entire worker thread suspended when there is the potential of blocking contention at lowest priority, would it be preferable for a throttle style of operation (a portion of time active, with brief periods of inaction)?
I tend to leave lots of Chrome tabs active all the time.

Throttling=xx(%)

Put this in prime.txt, as in 'throttling=90'

The problem some see in this solution is that it works by pausing workers for the specified amount. In the example above, workers pause for 10% of the time. This causes constant temperature fluctuations in the CPU, which increases stress on its structure.

[QUOTE=kladner;380147]Throttling=xx(%)

Put this in prime.txt, as in 'throttling=90'
[/QUOTE]

The line that I've sometimes used was spelled like:
[CODE]Throttle=33[/CODE]

I read this thread after a several minutes widespread process blockage following a reboot today, but I don't really know the cause, and it came good.
I don't see any of the vast number of chrome threads with priority below 6.
Maybe some malware checking agent interplay was blocking for me?
I was thinking more like 99% duty. I don't really expect a thread should rely on any significant, perhaps rare, time slice at lowest priority.
I wouldn't think it reasonable that a browser window might block itself due to something it might put in play at lowest priority.

OUCH! You are correct about the syntax. Pardon my blooper. :gah:

[QUOTE=snme2pm1;380154]Maybe some malware checking agent interplay was blocking for me?[/QUOTE]
I am Firefox to my teeth, so again, take this with a grain of salt: it may not be chrome itself, but again some Adobe tools (see the discussion about Acrobat above). For example, some page uses Flash to play its animation, and if Chrome is waiting for some feedback from flash, and flash runs in idle pri.. You got the picture. This would justify why when you start Chrome everything is fine, but as long as you work and access "some" pages, with flash on them, etc... Not necessary flash, I use it as an example only. Do your own research before trusting me here :smile:

On the other aspects, I agree with you about Chrome updating policies. You can set it from somewhere to ask you before doing updates, but its mechanism is still very unsafe. In theory, Google can do whatever they like in your computer, or this is what my hacker [STRIKE]feelings[/STRIKE] friends are telling me. That is why I use Firefox, nothing is as good as an open browser... [URL="https://www.mozilla.org/en-US/firefox/desktop/fast/"]The speed[/URL] is secondary :smile:

I'd rather just shut the entire core down. It's working perfectly. It picks worker number four.