159oje

If it helps you track it down, I stumbled across a weird workaround - If you specify the debugger type as "Native Only" (as opposed to the default of "Auto"),...

Never mind - It's back again :(

I had tried that powertool before, but it doesn't see or attach to any of the chrome child processes when using F5, perhaps Chromium is doing something funky and non-standard...