EvalError: Possible side-effect in debug-evaluate in Google Chrome

I think I found the issue, reading through a discussion on an electron issues board.

It could potentially be caused by this: [inspector] Add custom error dispatch machinery for debug evaluate.

And hopefully fixed in this: [inspector] Don’t trigger window.onerror with side-effects disabled.

This was an oversight in https://crrev.com/c/3557234, which led to a really weird developer experience: once a window.onerror handler was installed, typing into the Console or other side-effect free debug evaluations triggered this handler.