Forum Discussion
Dev channel update to 90.0.796.0 is live
Yoneff and anybody else experiencing a white/hanging Edge, we've found that there's a particular flag that's causing this behavior. First, to make it so you can even get to the flags, start Edge from the command line with the --disable-gpu flag. Then, on edge://flags, click the button to reset all the flags to their default state. The flag in question is to force Edge's Color Profile, but that flag may be missing for some people, so the only way to reset it is to reset all of Edge's flags. In particular, that flag seems to be getting set to HDR10 for some people, and the hang occurs when that happens, so resetting it back to a non-HDR colorspace fixes Edge. For anybody this fix works for, please let me know!
josh_bodner This did not work for me
Jerry Bumgarner also, for anybody who's experiencing Edge being all-white/hanging at launch, we need your help to get some more data about this. If you're able to to eventually get Edge into a working state after seeing it be all white, please go to edge://gpu and send me the logs on that page. If you're not even able to get Edge into a working state, we'd love to have dumps of both the main browser and GPU process. To figure out which is which, go to the Details tab of Windows Task Manager, right-click the column headers, go to Select Columns, check the box for "Command Line", then sort the processes by name. Once you get to all the msedge.exe processes, the GPU process is the one with --type=gpu-process in its command line, and the main browser process is one that doesn't have any --type string (other types you'll see include crashpad-handler, utility, and renderer)
josh_bodner Attached are my logs.
Thanks for your work!
josh_bodner Edge eventually comes into a working state after @8 or 10 seconds. If I leave Edge open and try to launch again, it works fine.
