Forum Discussion

paolot's avatar
paolot
Brass Contributor
Aug 22, 2019
Solved

This page is having problems

Hello everybody! I started using Microsoft Edge Dev some months ago and everything went smoothly until today: I turned on my laptop, opened Edge Dev and noticed that it is not working anymore at a...
  • paolot's avatar
    paolot
    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-FRROME's avatar
V-FRROME
Iron Contributor
Aug 22, 2019

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.

dansauve's avatar
dansauve
Copper Contributor
Oct 02, 2019

V-FRROME 

 

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.

  • MBlue835's avatar
    MBlue835
    Copper Contributor
    Oct 07, 2019

    dansauve 

     

    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).

     

    • dansauve's avatar
      dansauve
      Copper Contributor
      Oct 09, 2019
      Thank you! I'll try this next time is if the issue persists. The issue I had with adding the arguments to the executable is that if I launched EdgeDev from a hyperlink (in Outlook for example) it still wouldn't work because those arguments aren't passed (even adter I ensured that allowing extensions from other stores was enabled).

      Luckily, seems like MS is listening and I see in this week's dev release v79.0.294.1 the following:

      "Temporarily disabled Renderer Code Integrity by default to prevent situations where it causes all tabs to crash upon loading."

      Hopefully this means that this shouldn't be an issue at all now even when Edge is launched without a shortcut including those arguments.
      • Peckmore's avatar
        Peckmore
        Copper Contributor
        Dec 05, 2019

        Just updated Edge Dev to Version 80.0.345.0 and I'm experiencing this issue again, so I've had to put the switch back in to disable Renderer Code Integrity:

         

        --disable-features=RendererCodeIntegrity

         

        Looking through the release notes for this version I can't see any explicit mention of this feature being enabled again, but it was stated previously that it was only disable temporarily, so it seems like it's now back? (Or it may have happened in a previous release that I missed?)

         

        Is there any more insight into fixing this issue?

Resources