Forum Discussion
Dev channel update to 81.0.381.0 is live
All of the installs with a bunch of folks that I have using it around here are receiving the fun white screen that sits for a good 10-seconds or more then eventually your see
This is on the Dev Channel, Beta and Canary are the only ones that work for us. I can't even go to "About Microsoft Edge".
All of the installs with a bunch of folks that I have using it around here are receiving the fun white screen that sits for a good 10-seconds or more then eventually your see
This is on the Dev Channel, Beta and Canary are the only ones that work for us. I can't even go to "About Microsoft Edge".
Hexxus adding MissyQ and Deleted for awareness since they're seeing users in other threads (and platforms) reporting this. The good news is that, if Canary is working for you, it's likely that this is fixed and the fix will make it into the next Dev update. Regardless, we're also keeping an eye on it and checking to see if there are any workarounds. The behavior sounds similar to the behavior described here: https://textslashplain.com/2019/09/27/aw-snap-every-tab-crashes/ (written by one of our engineers), although the particular cause(s) in that article seem different enough that I would be surprised if any of the workarounds mentioned there fix this for you.
josh_bodner - Still having that same issue with Canary. The strange thing is that Beta is working fine but Dev nor Canary are working. They both have the exact same error.
carlosmontanez since you're hitting the same STATUS_ACCESS_VIOLATION as samuele2, are you also using Forcepoint/Websense security software by any chance?
The suggestion to add --disable-features=RendererCodeIntegrity unfortunately does not change the broken behavior.
samuele2 Our investigation over the past week helped us figure out that some of the people hitting STATUS_ACCESS_VIOLATION have been running Forcepoint/Websense security software on their systems. By any chance, are you, and does disabling it make any difference?
Hexxus josh_bodner
Sure is going to be interesting to know why some are experiencing this behavior. Personally, I am anxious to hear the explanation, even though not seeing it myself. Still, keen & curious to learn what was behind it.
Cheers,
Drew- The same Status_Access_Violation_Error, it's in a super white font color that is barely readable.
