haaa! finally... after waiting for well over a week, at last! the bug *did* in fact reoccur. just to make sure we're on the right page this is from the chrome://version
Chromium 56.0.2924.76 (Developer Build) built on Debian 9.0, running on Debian 7.4 (64-bit) Revision 314da7cc1e56fc9fa9271bac2b029922feb4b6f2 now, here's the circumstances: * i was using facebook "chat" web variant (don't tell no-one in the software libre world that, ok? :) * CPU usage climbed *really* high - 3 processes each hit around 20% and the CPU speed had to jump to around 2ghz to cope (fans came up) * after flipping to a separate screen (i use fvwm) and returning.... ta-daaaa, freeze! so whatever has been added that "fixes" the problem does NOT actually fix the *ACTUAL* underlying race-condition / problem... it just avoids *most* circumstances where it occurs... but not all. l.
