All google based websites work fine, anything other than google does not load and gives the listed error messages.

Thank you for the report.

Request you to please share the crash id for these crashes for further investigation.
Navigate to chrome://crashes and grab the crash ids from there. Thanks!

543410756bf4583b
d487724f894550d5
a7a02b57277c192c
bbb7a8f7a9a10930
91340fd8ef0dc86f
1a6038f16e3f5030
35748e09186ca8e5

Thank you for providing more feedback. Adding requester "askatte@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Thank you for the crash ids. They were helpful.

can you please take a look or help triaging? Crash reports pointed to https://chromium.googlesource.com/chromium/src.git/+/177d44c2b478ca96d5cff47940509b578e4af697 as the culprit CL.

Unfortunately i do not know what to do from here.

Sorry for the confusion. Owner of the bug will be taking care of the issue now.

Re comment 5: That change is not the offender.

Actually, the stack trace is so weird (it has only one line), and I don't
understand what's happening.

According to the stack trace, this *seems* related to IntersectionObserver.
szager, do you have any idea?

I don't think this is a bug in IntersectionObserver.  Without a stack trace, it's hard to say what's going on.  The crash is a SIGILL (illegal instruction), which is pretty weird.  I couldn't find any more crash reports aside from the ones listed in comment #3, which leads me to believe that this likely not a bug in chrome.

SIGILL suggests a CHECK failure, so we are probably hitting a CHECK in
Vector<>::at(), as the stack suggests. I don't know if there's a code path
using at() from IntersectionObserver ctor.

The stack may perhaps be just bogus, though.

There doesn't seem to have been movement on this bug, so closing. Hopefully this isn't still happening; ask to re-open or file a new bug if so.