Todd,
On 2018-03-27 15:41, Todd Zullinger wrote:
Philip Rhoades wrote:
> On 2018-03-27 12:18, Samuel Sieb wrote:
>> If you run top, which process is using the CPU? Just kill that one,
>> then go through your chrome tabs and find out which tab has the sad
>> face on it.
>
> That usually doesn't work from my recollection, no individual tab
> seems to
> be a problem - it is either Chrome as a whole or a whole window I
> think . .
> obviously shutting down all of Chrome fixes the problem . . but it is
> a pain
> to gradually re-open all the windows I previously had open again . .
Times like that, 'chrome://restart' is handy. I use it most
often to pick up updates without waiting for Chrome to see
that it's been updated, but it works well in general.
I will have a look at that but I expect similarly to when Chrome crashes
with a dozen windows open and with a dozen tabs in each - responding by
clicking "Recover" to the "Chrome did not shut down properly" message
seems to be more likely to actually cause the problem I first posted
about . . If I have been more disciplined and have had a dozen windows
open but only a few tabs per window . . it is not so bad . . thankfully
the "Tabs Outliner" extension helps greatly (although I had to change
the way I normally worked).
Thanks,
P.
--
Philip Rhoades
PO Box 896
Cowra NSW 2794
Australia
E-mail: phil(a)pricom.com.au