Lukas Stracke

Hi @markivancho and thanks for reporting! I was able to reproduce this in the SDK version 7.0.0 with Chrome 102, too. I'll bring it up with the team and we'll...

Hi @markivancho, we found the reason why these errors are suddenly thrown. It's Chromium related starting with 102 (as you reported) and was possibly [introduced here](https://chromium-review.googlesource.com/c/v8/v8/+/3557234/). It was [fixed](https://chromium-review.googlesource.com/c/v8/v8/+/3660253) a...

Hey @markivancho (and everyone else who's getting these errors), we're still discussing how to best filter such browser-caused errors in the future automatically. In the meantime, you have a couple...

Admittedly it's been a while since I looked into this but I think the "feature" is that errors from the console are thrown to `window.onerror`. The "bug" though is that...

I'm going to close this issue for the time being, since it seems as if the provided workaround works well enough. Feel free to reach out/comment here if you have...

> I have 99% errors in my sentry list from users trying things out in their console This is a pretty good reason to reopen this issue ;) Thanks for...

Hi @firasdib @Irevall and everyone else, we investigated console errors a little more and we mostly came to the same conclusions. Unfortunately, there is no bullet-proof way of detecting if...

Thanks for the examples. I think most of them should be caught by the solution above. The `EvalError: Possible side-effect in debug-evaluate` could still be from the eager input bug...

Awesome, really glad to hear that this is working reasonably well for you! Also, thanks for providing your modified version. We'll keep an eye on the Chromium issue for now...

Hi @ozerovs, thanks for writing in! We had a quick look at this issue and there might be something wrong on our end. We still need to look into it...