Forum Discussion
This page is having problems
- Aug 22, 2019
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!
- V-FRROMEAug 22, 2019Iron Contributor
tharosfire paolot Anthony RetroChrisB Mark Heath
Thanks, everyone for reporting this issue.
I have reported this problem to the engineering team.
I'm curious if it's only affecting specific extensions, could you all please list an extension or two you where using?
Thanks for your patience,
Frank.
- dansauveOct 02, 2019Copper Contributor
I'm still having this issue, on both Dev and Beta channels, and it's happening on multiple computers (one personal, one corp). Both a Dell computers if that's worth anything (an XPS 13 2-in-1 7390 and a Latitude 7480), with Symantec Endpoint Protection on the work Latitude. As for extensions, I only have 2 - 1Password X and Momentum Dashboard.
The --disable-features=RendererCodeIntegrity flag does seem to fix it for me on both computers that is failing. Prior to this, I noticed that reinstalling would fix the problem for a while, but then it would just show up out of the blue for no reason when starting the app sometime... Pages wouldn't load, and even the About and Preferences wouldn't load.
- MBlue835Oct 07, 2019Copper Contributor
I have found that if I use the --disable-features=RendererCodeIntegrity", Edge works to at lease allow me to get into extensions. Once in Extensions, if I enable "Allow extensions from other stores" then remove the RendererCodeIntegrity switch, then the Edge issue seems to be resolved. I am using SEP 14.2.4814.1101 (aka 14.2 RU1 MP1).
- jbernieAug 24, 2019Copper Contributor
V-FRROME I did a report through the browser, was erroring on Cisco WebEx (v1.5 & latest) plugin from the Google store, the only one installed. However even with it disabled I still had the issue. Had the same issue on the Canary build, but Beta being a bit older remained fine.
Alternate to the flags, on Win10 if you put the browser in Win8 compatibility mode it works fine.
- RetroChrisBAug 23, 2019Copper Contributor
In my case the Chromium team think it's a known incompatibility between Symantec Endpoint Protection 14.0.3929.1200 and renderer code integrity. I am using that version of Symantec Endpoint Protection.
https://bugs.chromium.org/p/chromium/issues/detail?id=993099
I don't currently have any extensions installed
- texasRayAug 23, 2019Copper Contributor
Having the same problem on a work PC - we are using SEP as well.