Forum Discussion
Top feedback summary for September 24
9/24 release broke Beta version for me. Here's the screenshot of what I'm getting on every single site, even edge's own about page, it spins to infinity and eventually just stops with "This page is having a problem":
OS: Windows 10 Enterprise LTSC 1809 build 17763.737
Edge version: 78.0.276.11 (Official build) beta (64-bit)
The only thing that seems to be working as a workaround is to add this flag in the shortcut: "--disable-features=RendererCodeIntegrity"
I'm evaluating Edge Chromium for a company wide deployment once the stable version comes out and this bug doesn't give much confidence in the browser.
I do not know if "Aw, Snap" and "This page is having a problem" are the same. Does the problem also happen in Chrome 78?
This page, which I just stumbled on and remembered your post, says it may be due to Chrome's new sandboxing and security DLL injections?
https://textslashplain.com/2019/09/27/aw-snap-every-tab-crashes/
ikjadoon I was getting the "Aw, Snap" error message on Thursday with Chromium. It was 79.0.3925.0, and every updated batch that came out that day for 79.0.3925.0 kept/remaining the same message. Especially on youtube. It would load, and a few minutes later crash with the "Aw, Snap" message. When 79.0.3926.0 came out on Friday it was fine with no more of that error, and today Chromium is on 79.0.3927.0 and still fine. I noticed that "Aw, Snap" happens when there's a new bug or new bug from testing/tweaking a new feature that causes the browser to crash or crash in certain areas.
Chrome 78 is their "Beta" version that's updated every six weeks or so, but I think slightly ahead of Edge's updated "Beta" version in time frame. So they may or may not being having the same problem although Edge Beta is adding features not found in Chrome Beta thus something that might bug out in Edge Beta might not in Chrome Beta and vise versa. Simply because Chrome doesn't have that feature specific only too Edge or Chrome has that specific feature not found in Edge Chromium.
I guess the best thing to do is drop down to Edge Dev and/or Canary and see if the error is replicating on those browsers on your computer. If they aren't than it might be specific to Beta, if they are it could be a carry over bug or something only you're experiencing (especially if others dont report it) to your computer/settings.
