On 03/26/2018 06:53 PM, Philip Rhoades wrote:
On 2018-03-27 12:18, Samuel Sieb wrote:
On 03/26/2018 05:59 PM, Philip Rhoades wrote:
but it is not what I want to do - when Chrome goes mad and the whole
system starts grinding to a halt (I know from experience it is
Chrome) I want to try and work out what specific Chrome tab or window
is the problem. Chrome has its own task manager:
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 . .
As far as I can tell, there is one process per tab. So if there isn't a
specific process that causing the problem, then it must be one of the
core processes and there's nothing you can do but restart the whole thing.
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
