On Tue, Jan 24, 2017 at 5:44 PM, lkcl <l...@lkcl.net> wrote: > Package: chromium > Version: 55.0.2883.75-3 > Followup-For: Bug #848895
> i'm currently going through the list of processes killing them one by > one to see if that helps... ah ha! it does. okay so *one* of the processes is causing a lock-up of all the others. finally after issuing "kill {PID}" in succession on the (20) highest PIDs, *eventually* i got chromium back.... with 15 "aw snap" tabs... :) i can't tell you which one actually was responsible for the problem unless there's a way to find out which process is responsible for which URL. if you know how i can always run the exercise again... WHEN it happens again (not if....) l.