Forum Discussion
This page is having problems
RetroChrisB thanks for sharing. Reading the discussion about that issue I got rid of the previous flag ("-no-sandbox") and changed to "--disable-features=RendererCodeIntegrity" since that should be a little bit more secure.
Thanks!
I was having the issue a few days back with Edge Canary, but it's fine now after one of their daily updates. I've had it happen in Chrome Canary too and the same thing...usually by the next day update (or second next day update) it's fixed. Sometimes for whatever reason it carries into Dev. As others said there can be a specific reason or Windows reason for it happening (I don't know as Canary is working fine for me now, an I'm not on the Dev side of things).
You can also see if the same bug happens in Chromium:
(Keep in mind that Chromium is not meant to be used as an everyday or regular browser as it doesn't have auto updater or any updater except manually installing it everyday, and it lacks important codec that isn't built into it to run certain applications. So stick with Edge Canary/Dev/Beta for that, but it's good for testing to see if a bug is in the original source or for analyzing to see if an crashing issues found in the later versions like Canary and Dev are happening in the original trunk version). https://www.chromium.org/getting-involved/download-chromium