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.
_______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org
