Edge Beta black out

%3CLINGO-SUB%20id%3D%22lingo-sub-880675%22%20slang%3D%22en-US%22%3EEdge%20Beta%20black%20out%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-880675%22%20slang%3D%22en-US%22%3E%3CP%3EOn%20a%20new%20Surface%206%20Pro.%3C%2FP%3E%3CP%3EEdge%20Beta%20quite%20regularly%20goes%20black%2C%20the%20whole%20application.%20I%20can%20three%20finger%20swipe%20to%20see%20the%20desktop%20apps%20running%2C%20Edge%20Dev%20shows%20black%2C%20no%20other%20app%20exhibits%20this%20behavior.%20I%20can%20start%2Fstop%20all%20other%20apps%20and%20browsers%20without%20issue.%3CBR%20%2F%3Esometimes%20it%20will%20come%20back%2C%20but%20mostly%20not%20and%20i%20have%20to%20close%20the%20window.%3C%2FP%3E%3CP%3EWhen%20I%20close%20Edge%20Dev%2C%20sometimes%20it%20flashes%20on%20the%20display%20as%20it%20is%20closing%2C%20other%20times%20not%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EOn%20a%20completely%20unrelated%20issue%20-%20my%20work%20disallows%20the%20dev%20version%20but%20allows%20the%20beta%20version%20-%20I%20got%20the%20new%20beta%20version%20last%20week%20and%20now%20that%20is%20blocked%20-%20discussed%20with%20our%20client%20gpo%20guru%2C%20they%20haven't%20changed%20anything%20in%20that%20policy.%26nbsp%3B%20Possible%20the%20dev%20signature%20got%20pushed%20to%20the%20beta%20channel%3F%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-880722%22%20slang%3D%22en-US%22%3ERe%3A%20Edge%20Beta%20black%20out%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-880722%22%20slang%3D%22en-US%22%3EHi%2C%20Have%20you%20enabled%20any%20flags%3F%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-880832%22%20slang%3D%22en-US%22%3ERe%3A%20Edge%20Beta%20black%20out%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-880832%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F310193%22%20target%3D%22_blank%22%3E%40HotCakeX%3C%2FA%3E%26nbsp%3BFWIW%20(if%20Greg%20and%20I%20are%20in%20fact%20talking%20about%20the%20same%20symptom)%20no%2C%20I%20do%20not%20have%20any%20flags%20enabled.%20Checked%20by%20visiting%20edge%3A%2F%2Fflags%20and%20seeing%20that%20none%20of%20the%20dropdowns%20are%20highlighted.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20did%20a%20%22Reset%20all%20to%20defaults%22%26nbsp%3B%20just%20now%20in%20case%20I'd%20set%20a%20flag%20long%20ago%2C%20didn't%20remember%2C%20and%20the%20dropdowns%20being%20highlighted%20are%20a%20false%20negative%20for%20some%20reason.%20I'll%20let%20you%20know%20if%20it%20still%20occurs.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20also%20filed%20a%20bug%20report%20on%20this%20using%20the%20%22Send%20Feedback%22%20button%20earlier%20today.%20Unfortunately%20was%20not%20able%20to%20include%20this%20screenshot%20with%20the%20bug%20report%20since%20to%20use%20Send%20Feedback%20AFAIK%20I'd%20need%20to%20be%20able%20to%20see%20the%20button.%20%3A)%3C%2Fimg%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-880815%22%20slang%3D%22en-US%22%3ERe%3A%20Edge%20Beta%20black%20out%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-880815%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F19448%22%20target%3D%22_blank%22%3E%40Greg%20Hejl%3C%2FA%3E%26nbsp%3BDo%20you%20mean%20the%20Edge%20Beta%20window%20goes%20blank%2C%20like%20this%3F%3CBR%20%2F%3E%3CBR%20%2F%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F133961iD9A97582018A984F%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22edge-window-black.png%22%20title%3D%22edge-window-black.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIf%20so%2C%20yeah%2C%20this%20happens%20to%20me%20every%20couple%20days.%20I'm%20pretty%20sure%20it%20only%20occurs%20immediately%20after%20signing%20into%20the%20PC%2C%20after%20having%20left%20Edge%20Beta%20windows%20open%20in%20my%20previous%20session.%20(In%20between%20my%20sessions%2C%20other%20users%20probably%20returned%20to%20the%20lock%20screen%20and%20signed%20in%20themselves%2C%20and%20did%20who-knows-what...%20this%20is%20a%20family%20PC%20used%20by%20several%20people.)%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIt%20doesn't%20happen%20all%20the%20time%2C%20just%20sometimes.%26nbsp%3B%3CSPAN%3EI%20don't%20have%20trouble%20like%20this%20with%20other%20apps%2C%20just%20Edge%2C%20and%20I%20think%20this%20started%20occurring%26nbsp%3Ba%20few%20weeks%20ago%20on%20Beta%2C%20if%20not%20a%20month%20or%20so%20ago.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20can%20close%20Edge%20windows%20that%20get%20in%20this%20state%20by%20clicking%20in%20the%20upper%20right%20corner%20(where%20the%20close%20button%20should%20be)%2C%20or%20by%20closing%20windows%20from%20context%20menu%20on%20Edge's%20taskbar%20icon.%20After%20I%20do%20that%20and%20open%20a%20new%20Edge%20window%2C%20the%20new%20window%20is%20unaffected.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-880861%22%20slang%3D%22en-US%22%3ERe%3A%20Edge%20Beta%20black%20out%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-880861%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F45503%22%20target%3D%22_blank%22%3E%40Wade%20Dorrell%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EYou%20can%20take%20a%20screenshot%20via%20snip%20%26amp%3B%20sketch%20app%20in%20Windows%2010%20and%20upload%20it%20along%20with%20any%20other%20files%20you%20want%20(could%20be%20even%20more%20than%20one%20picture)%20with%20your%20feedback%20and%20send%20it%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-center%22%20style%3D%22width%3A%20397px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F133116iC527D2E9EF3A8DDA%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%222.png%22%20title%3D%222.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-center%22%20style%3D%22width%3A%20895px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F133117i4F79C4BE8B3F4581%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%223.png%22%20title%3D%223.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-center%22%20style%3D%22width%3A%20892px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F133118iB6B7FE679458BD9C%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%224.png%22%20title%3D%224.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-880872%22%20slang%3D%22en-US%22%3ERe%3A%20Edge%20Beta%20black%20out%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-880872%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F310193%22%20target%3D%22_blank%22%3E%40HotCakeX%3C%2FA%3E%26nbsp%3BAh%2C%20I%20had%20no%20idea%20the%20%22diagnostic%20data%22%20link%20would%20let%20me%20add%20screenshots.%20I'd%20never%20clicked%20it.%20Maybe%20%22diagnostic%20data%20or%20additional%20screenshots%22%20would%20be%20better%20text.%20I%20figured%20if%26nbsp%3B%3CEM%3Ecould%3C%2FEM%3E%20add%20screenshots%20(other%20than%20the%20current%20screen)%20it'd%20be%20part%20of%20the%20%22Include%20this%20screenshot%22%20bit.%20(I%20spent%20maybe%2030%20seconds%20trying%20to%20figure%20out%20if%20I%20could%20paste%20or%20drag%20a%20file%20into%20that.)%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAnyway%2C%20the%20screenshot%20%26amp%3B%20bug%20is%20described%20here%20adequately.%20Wish%20I%20had%20better%20steps%20short%20of%20%22leave%20some%20Edge%20windows%20open%20and%20sign%20out%2C%20walk%20away%2C%20later%20come%20back%20and%20sign%20in%22%20but%20that's%20all%20I've%20got%20for%20now.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1013384%22%20slang%3D%22en-US%22%3ERe%3A%20Edge%20Beta%20black%20out%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1013384%22%20slang%3D%22en-US%22%3E%3CP%3EFWIW%20this%20is%20still%20occurring%20occasionally.%20I%20saw%20it%20as%20recently%20as%20the%20beta-channel%20build%20of%20Edge%20that%20has%20the%20new%20%22wave%22%20icon.%20(I%20hesitate%20to%20state%20version%20%23%20since%20I%20don't%20know%20if%20it%20occurred%20on%20the%20exact%20version%20I%20have%20installed%20today%20or%20not%2C%20but%20the%20version%20I%20have%20installed%20today%20is%20%3CSPAN%3E79.0.309.18.%3C%2FSPAN%3E)%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIt%20would%20be%20helpful%20if%20someone%20from%20the%20team%20could%20acknowledge%20the%20symptom%20is%20known%2C%20and%20if%20it%20is%20known%20to%20be%20fixed%20in%20some%20version...%20then%20I%20will%20start%20paying%20more%20attention%20when%20it%20does%20occur%20again.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1013800%22%20slang%3D%22en-US%22%3ERe%3A%20Edge%20Beta%20black%20out%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1013800%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F19448%22%20target%3D%22_blank%22%3E%40Greg%20Hejl%3C%2FA%3E%26nbsp%3BI%20have%20seen%20this%20as%20well%2C%20I%20think%20it's%20the%20same%20symptom%20that%20was%20attributed%20to%20an%20issue%20with%20the%20browser's%20GPU%20process%20by%20MS%20recently.%20When%20this%20happens%2C%20hit%20shift-ESC%20on%20your%20keyboard%20(shows%20a%20browser-specific%20task%20manager)%2C%20sort%20by%20task%20name%20(click%20on%20the%20word%20'Task'%20in%20the%20top%20left)%20so%20things%20don't%20move%20around%2C%20single-click%20the%20item%20'GPU%20process'%20and%20click%20the%20'End%20process'%20button%20in%20the%20lower%20right.%20This%20will%20restart%20the%20GPU%20process%20and%20should%20fix%20the%20issue%20without%20breaking%20any%20open%20tabs.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EEdit%3A%20found%20the%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2FDiscussions%2FDev-channel-update-to-80-0-328-4-is-live%2Fm-p%2F1009437%22%20target%3D%22_self%22%3Epost%3C%2FA%3E%2C%20and%20tbh%20they%20don't%20mention%20the%20screen%20blackout%2C%20just%20the%20UI%20becoming%20unresponsive.%20If%20you%20see%20it%20happen%20again%2C%20try%20the%20GPU%20tip%20and%20let%20us%20know%20if%20it%20helped.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThis%20is%20what%20MS%20wrote%20in%20that%20post%3A%20%22%3CEM%3ESometimes%20the%20browser%20will%20appear%20to%20not%20respond%20to%20any%20user%20input%20(clicking%20or%20scrolling%20in%20webpages%20doesn%E2%80%99t%20do%20anything%2C%20hovering%20over%20UI%20doesn%E2%80%99t%20make%20it%20change)%2C%20but%20clicking%20on%20certain%20buttons%20still%20works%20(like%20the%20%E2%80%A6%20menu).%20The%20cause%20of%20this%20is%20due%20to%20an%20error%20in%20the%20GPU%20process%2C%20and%20opening%20the%20browser%20task%20manager%20(right-click%20near%20the%20window%20minimize%2Fmaximize%2Fclose%20buttons%20or%20hit%20shift%2Besc%20on%20the%20keyboard)%20will%20open%20a%20window%20that%20will%20allow%20you%20to%20end%20the%20GPU%20process%2C%20which%20will%20fix%20the%20issue.%3C%2FEM%3E%20%22%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1013890%22%20slang%3D%22pt-BR%22%3ERe%3A%20Edge%20Beta%20black%20out%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1013890%22%20slang%3D%22pt-BR%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F316839%22%20target%3D%22_blank%22%3E%40ChromeRefugee%3C%2FA%3E%3CBR%20%2F%3EI've%20been%20having%20this%20problem%20a%20lot%20after%20windows%20update%20to%201909%20in%20about%3A%20flags%2C%20because%20the%20DX9%20GPU%20definitely%20solves%20the%20problem%2C%20but%20you%20lose%20browser%20performance.%20%3CBR%20%2F%3EI%20performed%20this%20process%20of%20task%20manager%20and%20GPU%20and%20solves%20the%20problem%2C%20but%20sometimes%20it%20happens%20again%2C%20this%20is%20happening%20to%20me%20in%20all%20variants%20of%20the%20edge.%26nbsp%3B%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1019117%22%20slang%3D%22en-US%22%3ERe%3A%20Edge%20Beta%20black%20out%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1019117%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F316839%22%20target%3D%22_blank%22%3E%40ChromeRefugee%3C%2FA%3E%26nbsp%3BThanks%20for%20the%20tip%2C%20i'll%20try%20%3CSHIFT%3E%3CESC%3E.%3C%2FESC%3E%3C%2FSHIFT%3E%3C%2FP%3E%3CP%3EThis%20issue%20seems%20to%20be%20happening%20more%20frequently%20on%20my%20surface%20pro.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1019406%22%20slang%3D%22en-US%22%3ERe%3A%20Edge%20Beta%20black%20out%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1019406%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F19448%22%20target%3D%22_blank%22%3E%40Greg%20Hejl%3C%2FA%3E%26nbsp%3BI%20had%20the%20exact%20same%20issue%20come%20up%20with%20last%20week's%20build%3A%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2FDiscussions%2FDev-channel-update-to-80-0-328-4-is-live%2Fm-p%2F1012509%2Fhighlight%2Ftrue%23M17175%22%20target%3D%22_blank%22%3Ehttps%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2FDiscussions%2FDev-channel-update-to-80-0-328-4-is-live%2Fm-p%2F1012509%2Fhighlight%2Ftrue%23M17175%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe'll%20see%20%3CSTRONG%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2FDiscussions%2FDev-channel-update-to-80-0-334-2-is-live%2Fm-p%2F1018372%22%20target%3D%22_blank%22%20rel%3D%22noopener%22%3Ewhat%20happens%20with%20this%20week's%20dev%20build%20released%20today%3C%2FA%3E%3C%2FSTRONG%3E%2C%20though%20they%20mention%20a%20similar%20issue%20should%20be%20patched%20next%20week%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CUL%3E%3CLI%3E%3CEM%3ESometimes%20the%20browser%20will%20appear%20to%20not%20respond%20to%20any%20user%20input%20(clicking%20or%20scrolling%20in%20webpages%20doesn%E2%80%99t%20do%20anything%2C%20hovering%20over%20UI%20doesn%E2%80%99t%20make%20it%20change)%2C%20but%20clicking%20on%20certain%20buttons%20still%20works%20(like%20the%20%E2%80%A6%20menu).%20The%20cause%20of%20this%20is%20due%20to%20an%20error%20in%20the%20GPU%20process%2C%20and%20opening%20the%20browser%20task%20manager%20(right-click%20near%20the%20window%20minimize%2Fmaximize%2Fclose%20buttons%20or%20hit%20shift%2Besc%20on%20the%20keyboard)%20will%20open%20a%20window%20that%20will%20allow%20you%20to%20end%20the%20GPU%20process%2C%20which%20will%20fix%20the%20issue.%26nbsp%3B%20This%20issue%20was%20inherited%20from%20upstream%20Chromium%2C%20and%20a%20fix%20for%20it%20just%20went%20in%20upstream%2C%20so%20the%20next%20Dev%20update%20should%20have%20it.%3C%2FEM%3E%3C%2FLI%3E%3C%2FUL%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1029015%22%20slang%3D%22en-US%22%3ERe%3A%20Edge%20Beta%20black%20out%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1029015%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F310193%22%20target%3D%22_blank%22%3E%40HotCakeX%3C%2FA%3E%26nbsp%3B-%20Hi%20I've%20got%20a%20couple%20of%20dmp%20files%20from%20an%20Edge%20process%20that%20is%20in%20a%20race%20condition.%3C%2FP%3E%3CP%3EThese%20are%20created%20by%20the%20%3CCTRL%3E%3CALT%3E%3CESC%3E%20task%20manager%20for%20Edge.%26nbsp%3B%20Once%20I%20end%20this%20process%2C%20Edge%20begins%20displaying%20again.%3C%2FESC%3E%3C%2FALT%3E%3C%2FCTRL%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EDo%20you%20have%20an%20alternative%20location%20for%20upload%3F%26nbsp%3B%20The%20feedback%20application%20only%20allows%2025mb%20and%20the%20zip%20I%20prepared%20from%20the%20dmp's%20are%20250mb%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1029080%22%20slang%3D%22en-US%22%3ERe%3A%20Edge%20Beta%20black%20out%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1029080%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F19448%22%20target%3D%22_blank%22%3E%40Greg%20Hejl%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CBLOCKQUOTE%3E%3CHR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F19448%22%20target%3D%22_blank%22%3E%40Greg%20Hejl%3C%2FA%3E%26nbsp%3Bwrote%3A%3CBR%20%2F%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F310193%22%20target%3D%22_blank%22%3E%40HotCakeX%3C%2FA%3E%26nbsp%3B-%20Hi%20I've%20got%20a%20couple%20of%20dmp%20files%20from%20an%20Edge%20process%20that%20is%20in%20a%20race%20condition.%3C%2FP%3E%3CP%3EThese%20are%20created%20by%20the%20%3CCTRL%3E%3CALT%3E%3CESC%3E%20task%20manager%20for%20Edge.%26nbsp%3B%20Once%20I%20end%20this%20process%2C%20Edge%20begins%20displaying%20again.%3C%2FESC%3E%3C%2FALT%3E%3C%2FCTRL%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EDo%20you%20have%20an%20alternative%20location%20for%20upload%3F%26nbsp%3B%20The%20feedback%20application%20only%20allows%2025mb%20and%20the%20zip%20I%20prepared%20from%20the%20dmp's%20are%20250mb%3C%2FP%3E%3CHR%20%2F%3E%3C%2FBLOCKQUOTE%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EYou%20can%20upload%20it%20somewhere%20else%20like%20here%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fsend.firefox.com%2F%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fsend.firefox.com%2F%3C%2FA%3E%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fwww.upload.ee%2F%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fwww.upload.ee%2F%3C%2FA%3E%3C%2FP%3E%3CP%3Eand%20then%20give%20the%20link%20to%20them%20via%20the%20feedback%20section%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1052916%22%20slang%3D%22en-US%22%3ERe%3A%20Edge%20Beta%20black%20out%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1052916%22%20slang%3D%22en-US%22%3E%3CP%3EI%20saw%20this%20completely%20black%20window%20again%20today%20(build%2079.0.309.40%2C%20latest%20beta%20as%20of%2012%2F6.)%20As%20in%20every%20case%20I've%20seen%20it%20in%20the%20past%2C%20it%20happened%20as%20I%20was%20logging%20into%20Windows%2C%20when%20I'd%20left%20an%20Edge%20window%2Fsite%20open%20in%20a%20prior%20session.%20I've%20never%20seen%20it%20occur%20under%20any%20other%20circumstance.%3CBR%20%2F%3E%3CBR%20%2F%3EShift-Esc%20is%20NOT%20accessible%20when%20the%20window's%20in%20this%20state.%20When%20I%20press%20Shift-Esc%20(after%20giving%20the%20window%20focus%20by%20dragging%20its%20title%20bar%20area%20first)%20the%20browser%20task%20manager%20window%20doesn't%20appear.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ERight-clicking%20left%20of%20where%20the%20minimize%20button%20would%20be%2C%20to%20get%20the%20context%20menu%20that%20includes%20%22Browser%20task%20manager%22%2C%20DOES%20work%2C%20and%20surprisingly%20all%20I%20had%20to%20do%20after%20that%20was%20click%20%22Browser%20task%20manager%22...%20I%20didn't%20have%20to%20select%2Fend%20any%20process%20with%20it%20manually...%20to%20get%20the%20Edge%20window%20to%20resume%20drawing%20correctly.%3C%2FP%3E%3CP%3E%3CBR%20%2F%3E(BTW%2C%20I%20did%20confirm%20that%20Shift-Esc%20launches%20the%20task%20manager%20when%20Edge%20isn't%20blacked%20out.)%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1052958%22%20slang%3D%22en-US%22%3ERe%3A%20Edge%20Beta%20black%20out%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1052958%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F45503%22%20target%3D%22_blank%22%3E%40Wade%20Dorrell%3C%2FA%3E%26nbsp%3B%20Ah%2C%20dang.%20So%2C%20for%20me%2C%20the%20bug%20has%20essentially%20disappeared%20in%20the%20latest%20Dev%20release.%20I'm%20on%26nbsp%3B80.0.345.0%20(Official%20build)%20dev%20(64-bit)%20and%20I've%20not%20had%20it%20happen%20in%20at%20least%20a%20week.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIt's%20unusual%20the%20bug%20is%20happening%20on%20the%20beta%20build%2C%20when%20I'd%20thought%20this%20was%20a%20Dev-only%20bug%20(we're%20on%20Branch%2080%2C%20instead%20of%2079%20like%20Beta).%20It%26nbsp%3B%3CEM%3Ewas%3C%2FEM%3E%20fixed%20in%20the%20Dev%20build%2C%20from%20the%20latest%20release%20notes%3A%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FP%3E%3CUL%3E%3CLI%3E%3CEM%3EFixed%20an%20issue%20where%20the%20browser%20UI%20sometimes%20appears%20to%20hang%20or%20turn%20all%20black%2C%20but%20it%20still%20responds%20to%20input%20and%20can%20be%20fixed%20by%20killing%20the%20GPU%20process.%3C%2FEM%3E%3C%2FLI%3E%3C%2FUL%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI'm%20curious%20if%20your%20bug%20actually%20%3CEM%3E%3CU%3Eis%3C%2FU%3E%3C%2FEM%3E%20a%20separate%20bug%20in%20Beta%20that%20just%20happened%20to%20coincide%20with%20the%20Dev%20bug%3F%20Or%20was%20there%20a%20recent%20Beta%20update%2C%20too%2C%20and%20unfortunately%20the%20bug%20made%20it%20into%20that%20Beta%20build%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1054175%22%20slang%3D%22en-US%22%3ERe%3A%20Edge%20Beta%20black%20out%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1054175%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F45503%22%20target%3D%22_blank%22%3E%40Wade%20Dorrell%3C%2FA%3E%26nbsp%3BRight%2C%20I%20don't%20have%20that%20weird%20black-screen-but-UI%20visible%2C%20either.%20%3A(%3C%2Fimg%3E%20Mine%20was%20just%20a%20pure%20black%20box%3A%20no%20UI%20elements%2C%20but%20I%20could%20get%20Edge%20back%20via%20shift-escape%20and%20ending%20the%20GPU%20process%20(does%20that%20help%20yours%20any%3F)%3A%20%3CSTRONG%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2FDiscussions%2FDev-channel-update-to-80-0-328-4-is-live%2Fm-p%2F1012509%2Fhighlight%2Ftrue%23M17175%22%20target%3D%22_blank%22%20rel%3D%22noopener%22%3Eidentical%20to%20this%20thread's%20screenshot%3C%2FA%3E%3C%2FSTRONG%3E.%20For%20the%20pure-black-box%20bug%2C%20I've%20not%20had%20that%20again%20since%20the%20latest%20dev%20update.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAgreed.%20I%20think%20someone%20from%20the%20MS%20team%20should%20respond%2C%20unless%20there%20are%20other%20issues.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAnother%20shot%20in%20the%20dark%3A%20I%20recently%20updated%20the%20NVIDIA%20drivers%20on%20that%20machine%3A%20maybe%20I'd%20confused%20causation%2Fcorrelation%20here%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1053110%22%20slang%3D%22en-US%22%3ERe%3A%20Edge%20Beta%20black%20out%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1053110%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F333743%22%20target%3D%22_blank%22%3E%40ikjadoon%3C%2FA%3E%26nbsp%3BI%20can%20say%20I've%20been%20seeing%20this%20%22100%25%20blank%20%26amp%3B%20black%20Edge%20window%20after%20login%22%20symptom%20consistently%20since%20Beta%2078%2C%20and%20possibly%20Beta%2077%2C%20although%20I%20didn't%20record%20build%20number%20for%20myself%20in%20either%20case%2C%20so%20I%20can't%20say%20exact%20build%2Frevision.%20It%20could%20not%20have%20been%20later%20than%20Beta%2078%2C%20though%2C%20based%20on%20the%20dates%20in%20this%20thread.%20I%20used%20built-in%20feedback%20reporting%20when%20I%20reported%20in%20late%20September%2C%20so%20Microsoft%20should%20know%20the%20specific%20version.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EInterestingly%2C%20I've%20never%20seen%20the%20symptom%20as%20reported%20in%2080%20known%20issues%20(%22Edge%20window%20UI%20stops%20responding%20and%20goes%20dark%20%5Bbut%20UI%2C%20like%20parts%20of%20tabs%2C%20context%20menu%2C%20%22...%22%20button%20is%20still%20visible%5D%22)%20as%20shown%20in%20others'%20screenshots%20of%20Dev%2079%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2FDiscussions%2FMS-Edge-stops-displaying-visual-content%2Fm-p%2F970696%22%20target%3D%22_self%22%3Ehere%2C%3C%2FA%3E%26nbsp%3Bor%20as%20explained%20in%20known%20issues%20as%20part%20of%20the%20workaround.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAs%20only%20the%20later%20symptoms%20were%20described%20in%20known%20issues%2C%20then%20blamed%20on%20Chromium%2C%26nbsp%3BI%20feel%20less%20than%20confident%20the%20former%20symptom's%20fixed.%20It's%20older%2C%20it%20occurs%20under%20very%20specific%20circumstances%2C%20it%20looks%20different%2C%20and%20they've%20had%20plenty%20of%20time%20to%20fix%20it%20in%2079%20if%20it%20was%20really%20known.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1095152%22%20slang%3D%22en-US%22%3ERe%3A%20Edge%20Beta%20black%20out%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1095152%22%20slang%3D%22en-US%22%3E%3CP%3ESaw%20this%20behavior%20again%20today%20on%20Edge%26nbsp%3B79.0.309.58%20(latest%20Beta%20build%20as%20of%20Jan%206%202020)%20when%20logging%20into%20existing%20Windows%20login%20session.%20As%20previously%2C%20I%20right%20clicked%20on%20the%20title%20bar%20area%20to%20get%20to%20Browser%20task%20manager%2C%20and%20upon%20opening%20Browser%20task%20manager%20the%20Edge%20window%20stopped%20being%20all%20black.%26nbsp%3B(I%20didn't%20even%20have%20to%20kill%20GPU%20Process.)%20I%20reported%20the%20same%20through%20the%20built-in%20%22Send%20feedback%22%20command.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1098835%22%20slang%3D%22en-US%22%3ERe%3A%20Edge%20Beta%20black%20out%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1098835%22%20slang%3D%22en-US%22%3E%3CP%3EI've%20been%20having%20these%20black%20screens%20for%20a%20while%20now.%3C%2FP%3E%3CP%3EI'm%20currently%20on%20the%20Dev%20branch%2C%20version%26nbsp%3B%3CSPAN%3E81.0.381.0%2C%20and%20I%20still%20am%20experiencing%20these.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EReading%20this%20thread%20helped%20me%20realize%20it's%20indeed%20a%20process%20using%20the%20GPU%20that%20hangs%20Edge.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3EI've%20noticed%20that%20there's%20a%20period%20in%20which%20the%20UI%20is%20not%20drawing%20(therefore%20the%20black%20window)%20but%20the%20app%20is%20still%20somewhat%20responsive.%20For%20example%2C%20I%20can%20switch%20the%20tabs%20by%20Ctrl%20%2B%20Tab%20and%20in%20my%20taskbar%20the%20title%20of%20the%20app%20changes%20accordingly.%20But%20after%20a%20few%20seconds%20Edge%20freezes%20and%20Windows%20asks%20me%20if%20I%20want%20to%20kill%20it.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EI've%20been%20trying%20to%20bring%20Edge's%20Task%20Manager%20up%20(i.e.%20Shift%20%2B%20Esc)%2C%20with%20varying%20success.%20Sometimes%20I%20can%20terminate%20the%20GPU%20process%2C%20sometimes%20it%20tries%20to%20show%20me%20the%20Task%20Manager%20window%20and%20promptly%20crashes%2C%20sometimes%20it%20shows%20me%20another%20black%20screen.%20%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3EWhat%20has%20been%20working%20reliably%20for%20me%20since%20reading%20this%20is%20bringing%20up%20Task%20Manager%20(i.e.%20Ctrl%20%2B%20Shift%20%2B%20Esc)%20and%20killing%20the%20process%20labeled%20Microsoft%20Edge%20that%20is%20taking%20up%20GPU%20resources.%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1137986%22%20slang%3D%22en-US%22%3ERe%3A%20Edge%20Beta%20black%20out%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1137986%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F511900%22%20target%3D%22_blank%22%3E%40thelinkin3000%3C%2FA%3E%26nbsp%3BI%20have%20stayed%20on%2079%20(on%20the%20release%20channel%20now)%20and%20the%20issue%20persists.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIn%20all%20the%20occurrences%20I've%20seen%20I've%20not%20yet%20had%20to%20kill%20GPU%20Process%20to%20restore%20functionality.%20Merely%20bringing%20up%20Browser%20Task%20Manager%2C%20seeing%20GPU%20Process%20running%20there%20but%20without%20doing%20anything%20to%20it%2C%20is%20sufficient%20to%20get%20the%20main%20Edge%20window(s)%20to%20un-black%2C%20and%20after%20that%20they're%20OK.%20I%20believe%20GPU%20process%20start%20time%20is%20quite%20old%2C%20and%20continues%20to%20be%20after%20the%20window's%20restored%2C%20although%20I'll%20confirm%20this%20next%20time%20(so%20I%20think%20it's%20not%20a%20case%20of%20the%20process%20having%20died%2Frespawned.)%20The%20other%20odd%20thing%20I've%20noted%20before%20is%20I've%20been%20unable%20to%20launch%20the%20Browser%20Task%20Manager%20using%20%22Shift-Esc%22%20even%20when%20the%20window%20appears%20to%20be%20in%20focus...%20I%20have%20to%20use%20the%20right-click%20menu%20near%20where%20the%20minimize%2Fclose%20windows%20would%20be.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAs%20such%2C%20wonder%20if%20my%20case%20of%20%22black%20out%22%20and%20your%20case%20of%20%22black%20out%22%20are%20actually%20the%20same.%20(My%26nbsp%3B%20symptoms%20I'd%20associate%20with%20something%20being%20wrong%20with%20how%20window%20messages%20are%20handled%2C%20not%20with%20some%20death%20of%20the%20GPU%20process.)%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIf%20there%20is%20any%20information%20I%20can%20collect%2C%20Microsoft%20reps%2C%20please%20chime%20in%2C%20since%20it%20seems%20this%20problem%20has%20persisted%20to%20the%20first%20stable%20release.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1170358%22%20slang%3D%22en-US%22%3ERe%3A%20Edge%20Beta%20black%20out%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1170358%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F511900%22%20target%3D%22_blank%22%3E%40thelinkin3000%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20way%20I%20found%20to%20fix%20it%20when%20it%20happens%2C%20is%20to%20open%20a%20new%20instance%20of%20edge%20without%20closing%20the%20previous%20one%2C%20as%20that%20seems%20to%20restart%20the%20GPU%20process%20and%20then%20the%20previous%20instance%20is%20visible%20again.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1459664%22%20slang%3D%22en-US%22%3ERe%3A%20Edge%20Beta%20black%20out%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1459664%22%20slang%3D%22en-US%22%3E%3CP%3EHere's%20a%20solution%20to%20the%20problem%20%3A%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fyoutu.be%2FrEpvoSHhBaQ%22%20target%3D%22_self%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fyoutu.be%2FrEpvoSHhBaQ%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
New Contributor

On a new Surface 6 Pro.

Edge Beta quite regularly goes black, the whole application. I can three finger swipe to see the desktop apps running, Edge Dev shows black, no other app exhibits this behavior. I can start/stop all other apps and browsers without issue.
sometimes it will come back, but mostly not and i have to close the window.

When I close Edge Dev, sometimes it flashes on the display as it is closing, other times not

 

On a completely unrelated issue - my work disallows the dev version but allows the beta version - I got the new beta version last week and now that is blocked - discussed with our client gpo guru, they haven't changed anything in that policy.  Possible the dev signature got pushed to the beta channel? 

21 Replies
Highlighted
Hi, Have you enabled any flags?
Highlighted

@Greg Hejl Do you mean the entire Edge Beta window goes black & blank, like this?

edge-window-black.png

 

If so, yeah, this happens to me every couple days. I'm pretty sure it only occurs immediately after signing into the PC, after having left Edge Beta windows open in my previous session. (In between my sessions, other users probably returned to the lock screen and signed in themselves, and did who-knows-what... this is a family PC used by several people.)

 

It doesn't happen all the time, just sometimes. I don't have trouble like this with other apps, just Edge, and I think this started occurring a few weeks ago on Beta, if not a month or so ago.

 

I can close Edge windows that get in this state by clicking in the upper right corner (where the close button should be), or by closing windows from context menu on Edge's taskbar icon. After I do that and open a new Edge window, the new window is unaffected.

Highlighted

@HotCakeX FWIW (if Greg and I are in fact talking about the same symptom) no, I do not have any flags enabled. Checked by visiting edge://flags and seeing that none of the dropdowns are highlighted.

 

I did a "Reset all to defaults"  just now in case I'd set a flag long ago, didn't remember, and the dropdowns being highlighted are a false negative for some reason. I'll let you know if it still occurs.

 

I also filed a bug report on this using the "Send Feedback" button earlier today. Unfortunately was not able to include this screenshot with the bug report since to use Send Feedback AFAIK I'd need to be able to see the button. :)

Highlighted

@Wade Dorrell 

 

You can take a screenshot via snip & sketch app in Windows 10 and upload it along with any other files you want (could be even more than one picture) with your feedback and send it:

 

2.png

 

3.png

 

4.png

 

Highlighted

@HotCakeX Ah, I had no idea the "diagnostic data" link would let me add screenshots. I'd never clicked it. Maybe "diagnostic data or additional screenshots" would be better text. I figured if could add screenshots (other than the current screen) it'd be part of the "Include this screenshot" bit. (I spent maybe 30 seconds trying to figure out if I could paste or drag a file into that.)

 

Anyway, the screenshot & bug is described here adequately. Wish I had better steps short of "leave some Edge windows open and sign out, walk away, later come back and sign in" but that's all I've got for now.

Highlighted

FWIW this is still occurring occasionally. I saw it as recently as the beta-channel build of Edge that has the new "wave" icon. (I hesitate to state version # since I don't know if it occurred on the exact version I have installed today or not, but the version I have installed today is 79.0.309.18.)

 

It would be helpful if someone from the team could acknowledge the symptom is known/not-known, and if there is/is-not a fix version... then I will start paying more attention when it does occur again. (If you think you already have it fixed and I just don't have that version yet, then I will not waste my time.)

Highlighted

@Greg Hejl I have seen this as well, I think it's the same symptom that was attributed to an issue with the browser's GPU process by MS recently. When this happens, hit shift-ESC on your keyboard (shows a browser-specific task manager), sort by task name (click on the word 'Task' in the top left) so things don't move around, single-click the item 'GPU process' and click the 'End process' button in the lower right. This will restart the GPU process and should fix the issue without breaking any open tabs.

 

Edit: found the post, and tbh they don't mention the screen blackout, just the UI becoming unresponsive. If you see it happen again, try the GPU tip and let us know if it helped. 

 

This is what MS wrote in that post: "Sometimes the browser will appear to not respond to any user input (clicking or scrolling in webpages doesn’t do anything, hovering over UI doesn’t make it change), but clicking on certain buttons still works (like the … menu). The cause of this is due to an error in the GPU process, and opening the browser task manager (right-click near the window minimize/maximize/close buttons or hit shift+esc on the keyboard) will open a window that will allow you to end the GPU process, which will fix the issue. "

Highlighted

@ChromeRefugee  
I've been having this problem a lot after windows update to 1909 in about: flags, because the DX9 GPU definitely solves the problem, but you lose browser performance.
I performed this process of task manager and GPU and solves the problem, but sometimes it happens again, this is happening to me in all variants of the edge.

Highlighted

@ChromeRefugee Thanks for the tip, i'll try <shift><esc>.

This issue seems to be happening more frequently on my surface pro.

Highlighted

@Greg Hejl I had the exact same issue come up with last week's build: https://techcommunity.microsoft.com/t5/Discussions/Dev-channel-update-to-80-0-328-4-is-live/m-p/1012...

 

We'll see what happens with this week's dev build released today, though they mention a similar issue should be patched next week:

 

  • Sometimes the browser will appear to not respond to any user input (clicking or scrolling in webpages doesn’t do anything, hovering over UI doesn’t make it change), but clicking on certain buttons still works (like the … menu). The cause of this is due to an error in the GPU process, and opening the browser task manager (right-click near the window minimize/maximize/close buttons or hit shift+esc on the keyboard) will open a window that will allow you to end the GPU process, which will fix the issue.  This issue was inherited from upstream Chromium, and a fix for it just went in upstream, so the next Dev update should have it.
Highlighted

@HotCakeX - Hi I've got a couple of dmp files from an Edge process that is in a race condition.

These are created by the <ctrl><alt><esc> task manager for Edge.  Once I end this process, Edge begins displaying again.

 

Do you have an alternative location for upload?  The feedback application only allows 25mb and the zip I prepared from the dmp's are 250mb

Highlighted

@Greg Hejl 


@Greg Hejl wrote:

@HotCakeX - Hi I've got a couple of dmp files from an Edge process that is in a race condition.

These are created by the <ctrl><alt><esc> task manager for Edge.  Once I end this process, Edge begins displaying again.

 

Do you have an alternative location for upload?  The feedback application only allows 25mb and the zip I prepared from the dmp's are 250mb


 

You can upload it somewhere else like here

https://send.firefox.com/

https://www.upload.ee/

and then give the link to them via the feedback section

Highlighted

I saw this completely black window again today (build 79.0.309.40, latest beta as of 12/6.) As in every case I've seen it in the past, it happened as I was logging into Windows, when I'd left an Edge window/site open in a prior session. I've never seen it occur under any other circumstance.

Shift-Esc is NOT accessible when the window's in this state. When I press Shift-Esc (after giving the window focus by dragging its title bar area first) the browser task manager window doesn't appear.

 

Right-clicking left of where the minimize button would be, to get the context menu that includes "Browser task manager", DOES work, and surprisingly all I had to do after that was click "Browser task manager"... I didn't have to select/end any process with it manually... to get the Edge window to resume drawing correctly.


(BTW, I did confirm that Shift-Esc launches the task manager when Edge isn't blacked out.)

Highlighted

@Wade Dorrell  Ah, dang. So, for me, the bug has essentially disappeared in the latest Dev release. I'm on 80.0.345.0 (Official build) dev (64-bit) and I've not had it happen in at least a week.

 

It's unusual the bug is happening on the beta build, when I'd thought this was a Dev-only bug (we're on Branch 80, instead of 79 like Beta). It was fixed in the Dev build, from the latest release notes:

  • Fixed an issue where the browser UI sometimes appears to hang or turn all black, but it still responds to input and can be fixed by killing the GPU process.

 

I'm curious if your bug actually is a separate bug in Beta that just happened to coincide with the Dev bug? Or was there a recent Beta update, too, and unfortunately the bug made it into that Beta build?

 

Highlighted

@ikjadoon I can say I've been seeing this "100% blank & black Edge window after login" symptom consistently since Beta 78, and possibly Beta 77, although I didn't record build number for myself in either case, so I can't say exact build/revision. It could not have been later than Beta 78, though, based on the dates in this thread. I used built-in feedback reporting when I reported in late September, so Microsoft should know the specific version.

 

Interestingly, I've never seen the symptom as reported in 80 known issues ("Edge window UI stops responding and goes dark [but UI, like parts of tabs, context menu, "..." button is still visible]") as shown in others' screenshots of Dev 79 here, or as explained in known issues as part of the workaround.

 

As only the later symptoms were described in known issues, then blamed on Chromium, I feel less than confident the former symptom's fixed. It's older, it occurs under very specific circumstances, it looks different, and they've had plenty of time to fix it in 79 if it was really known.

Highlighted

@Wade Dorrell Right, I don't have that weird black-screen-but-UI visible, either. :( Mine was just a pure black box: no UI elements, but I could get Edge back via shift-escape and ending the GPU process (does that help yours any?): identical to this thread's screenshot. For the pure-black-box bug, I've not had that again since the latest dev update.

 

Agreed. I think someone from the MS team should respond, unless there are other issues.

 

Another shot in the dark: I recently updated the NVIDIA drivers on that machine: maybe I'd confused causation/correlation here?

 

Highlighted

Saw this behavior again today on Edge 79.0.309.58 (latest Beta build as of Jan 6 2020) when logging into existing Windows login session. As previously, I right clicked on the title bar area to get to Browser task manager, and upon opening Browser task manager the Edge window stopped being all black. (I didn't even have to kill GPU Process.) I reported the same through the built-in "Send feedback" command.

Highlighted

I've been having these black screens for a while now.

I'm currently on the Dev branch, version 81.0.381.0, and I still am experiencing these.

 

Reading this thread helped me realize it's indeed a process using the GPU that hangs Edge.

I've noticed that there's a period in which the UI is not drawing (therefore the black window) but the app is still somewhat responsive. For example, I can switch the tabs by Ctrl + Tab and in my taskbar the title of the app changes accordingly. But after a few seconds Edge freezes and Windows asks me if I want to kill it.

 

I've been trying to bring Edge's Task Manager up (i.e. Shift + Esc), with varying success. Sometimes I can terminate the GPU process, sometimes it tries to show me the Task Manager window and promptly crashes, sometimes it shows me another black screen.

What has been working reliably for me since reading this is bringing up Task Manager (i.e. Ctrl + Shift + Esc) and killing the process labeled Microsoft Edge that is taking up GPU resources.

Highlighted

@thelinkin3000 I have stayed on 79 (on the release channel now) and the issue persists.

 

In all the occurrences I've seen I've not yet had to kill GPU Process to restore functionality. Merely bringing up Browser Task Manager, seeing GPU Process running there but without doing anything to it, is sufficient to get the main Edge window(s) to un-black, and after that they're OK. I believe GPU process start time is quite old, and continues to be after the window's restored, although I'll confirm this next time (so I think it's not a case of the process having died/respawned.) The other odd thing I've noted before is I've been unable to launch the Browser Task Manager using "Shift-Esc" even when the window appears to be in focus... I have to use the right-click menu near where the minimize/close windows would be.

 

As such, wonder if my case of "black out" and your case of "black out" are actually the same. (My  symptoms I'd associate with something being wrong with how window messages are handled, not with some death of the GPU process.)

 

If there is any information I can collect, Microsoft reps, please chime in, since it seems this problem has persisted to the first stable release.