Edge Crashes Consistently Upon opening DevTools

Issue #16462235 • Assigned to Bogdan B.

Details

Author
Olivier C.
Created
Mar 19, 2018
Privacy
This issue is public.
Found in
  • Microsoft Edge
Found in build #
41.16299
Reports
Reported by 8 people

Sign in to watch or report this issue.

Steps to reproduce

I am developing an Angular 4/5 application and trying to debug some weird issues occuring only on Edge. It is currently impossible to debug, as as soon as the DevTools are opened, the browser freeze/crash and the page reloads automatically after 10-15 seconds.

This is incredibly frustrating, and if we cannot get around this issue, I “fear” that we might have to simply alert our users that we don’t support MS Edge and they should use any other browsers…

I checked the Event Viewer to try and get more infos about the cause, but it’s not exactly helpful, at least for me. Two events are logged: Application Error, and Windows Error Reporting. I includes both XML below for your viewing pleasure.

It feels like the issue lie in something our code (or 3rd party) is doing, as I couldn’t replicate the problem with an “empty app” using the same stack. The significant libraries we’re using:
Angular 4 (also tested 5, same issue)
NGRX 2/4
RXJS 5
Radiant Media Player

Any kind of pointer to help isolate the problem are welcome.

You can reproduce the issue by going to this NSWF Link and opening the DevTools.

Application Error:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
  <Provider Name="Application Error" /> 
  <EventID Qualifiers="0">1000</EventID> 
  <Level>2</Level> 
  <Task>100</Task> 
  <Keywords>0x80000000000000</Keywords> 
  <TimeCreated SystemTime="2018-03-19T16:23:11.297968700Z" /> 
  <EventRecordID>1075</EventRecordID> 
  <Channel>Application</Channel> 
  <Computer>Redacted</Computer> 
  <Security /> 
  </System>
<EventData>
  <Data>MicrosoftEdgeCP.exe</Data> 
  <Data>11.0.16299.251</Data> 
  <Data>5a8e0cb4</Data> 
  <Data>edgehtml.dll</Data> 
  <Data>11.0.16299.251</Data> 
  <Data>cda73cb0</Data> 
  <Data>c0000602</Data> 
  <Data>0000000000363634</Data> 
  <Data>2b60</Data> 
  <Data>01d3bf9e7792ab74</Data> 
  <Data>C:\Windows\SystemApps\Microsoft.MicrosoftEdge_8wekyb3d8bbwe\MicrosoftEdgeCP.exe</Data> 
  <Data>C:\Windows\SYSTEM32\edgehtml.dll</Data> 
  <Data>8e4bd8cc-de62-4eb8-9d07-b3ffef9d116b</Data> 
  <Data>Microsoft.MicrosoftEdge_41.16299.248.0_neutral__8wekyb3d8bbwe</Data> 
  <Data>ContentProcess</Data> 
  </EventData>
  </Event>

Windows Error Reporting:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Windows Error Reporting" /> 
    <EventID Qualifiers="0">1001</EventID> 
    <Level>4</Level> 
    <Task>0</Task> 
    <Keywords>0x80000000000000</Keywords> 
    <TimeCreated SystemTime="2018-03-19T16:23:28.455682300Z" /> 
    <EventRecordID>1076</EventRecordID> 
    <Channel>Application</Channel> 
    <Computer>Redacted</Computer> 
  <Security /> 
</System>
<EventData>
  <Data>2046632318873827605</Data> 
  <Data>5</Data> 
  <Data>MoAppCrash</Data> 
  <Data>Not available</Data> 
  <Data>0</Data> 
  <Data>Microsoft.MicrosoftEdge_41.16299.248.0_neutral__8wekyb3d8bbwe</Data> 
  <Data>praid:ContentProcess</Data> 
  <Data>11.0.16299.251</Data> 
  <Data>5a8e0cb4</Data> 
  <Data>edgehtml.dll</Data> 
  <Data>11.0.16299.251</Data> 
  <Data>cda73cb0</Data> 
  <Data>c0000602</Data> 
  <Data>0000000000363634</Data> 
  <Data /> 
  <Data>\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1EEC.tmp.mdmp \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5D00.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5D00.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5D21.tmp.txt</Data> 
  <Data>C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_Microsoft.Micros_9b4e88961416e6591d2d36d56ca5ca705d7aaf4_1f8779cf_3edb605a</Data> 
  <Data /> 
  <Data>0</Data> 
  <Data>8e4bd8cc-de62-4eb8-9d07-b3ffef9d116b</Data> 
  <Data>268435456</Data> 
  <Data>8d84e0bd5a50e2032c671940204ef915</Data> 
  </EventData>
  </Event>

Attachments

0 attachments

    Comments and activity

    • Feedback-Hub (insider / en-us) = https://aka.ms/Jlbdko

    • Microsoft Edge Team

      Changed Assigned To to “Bogdan B.”

    • Seeing the same thing. I have created a .zip with the HTML and supporting files (saved page as files) and it consistently crashes Edge dev tools. To repro, Inspect the toolbar, which is a header element. Inside this header, there is a div. When you click the div to inspect it, dev tools crashes.

      This WeTransfer is valid for one week:
      https://we.tl/YGKQ65wQNh
      You can download the zip from here.

    • Stijn:
      I downloaded your zip but could not repro the problem
      I can inspect the app properly, whether or not I click the mentioned div (tried a few different ones for good measure)

    • Darn it. I should have tested the zip separately. You are right, with the zip I don’t see the issue! I saved the page crashing Dev Tools as zip because it is an in development project and I cant show it easily otherwise. I did not think to check it seperately, sorry.

      What I do see: 2 errors about Webpack stuff not being defined. I am using Webpack Dev Server in my project and when I try to inspect the running page (on localhost) Edge Dev Tools crashes… But not on the zip that does not have a connection to Webpack Dev Server… So my current guess is that this has something to do with Webpack Dev Server running and updating the page in the background…

      Do you have any tips that would allow me to give you better information?

      When this project is a bit further along I will create a live server with it. If the problem is present there also, I will update here.

    • I created a new zip by making a build from the app and zipping that. If you unzip to some folder and then open the index.html file it should give you something of an app shell kind of thing. Then open developer tools and try to inspect the div inside the header element. I tried this a couple of times and for me it crashes consistently every time I try to select that div.

      https://we.tl/l0wJheHIYG

    • Can anyone have another look? Should be reproducible with the new zip.

    • This codepen exhibits the same problem for me:
      https://codepen.io/StijnDeWitt/pen/gKMNMJ

    • Hi, I have the same problem during inspection of Angular elements. Has anyone found a solution? Thanks a million.

    • I am getting this against Microsoft Edge 42.17134.1.0 on a VM (windows free EDGE build 17134) which you can download here (https://developer.microsoft.com/en-us/microsoft-edge/tools/vms/). I am running on virtual box on mac high sierra. Every time i hit f12 or try to access developer tools through the settings menu the developer tools crashes.

      Here is the event viewer message:
      I am getting this against Microsoft Edge 42.17134.1.0 on a VM (windows free EDGE build 17134) which you can download here (https://developer.microsoft.com/en-us/microsoft-edge/tools/vms/). I am running on virtual box on mac high sierra. Every time i hit f12 or try to access developer tools through the settings menu the developer tools crashes.

      really need this to test apps to run on edge.

    • I just found this fix here https://developer.microsoft.com/en-us/microsoft-edge/platform/issues/18153935/ and it is working again:

      Run the following in powershell:

      Add-AppxPackage -register “C:\windows\SystemApps\Microsoft.MicrosoftEdgeDevToolsClient_8wekyb3d8bbwe\AppxManifest.xml” -DisableDevelopmentMode -Confirm:$false

    • Hi, thanks but that fix doesn’t work for me.
      The problem seems depend inserting sticky elements in scrolling elements.
      Has anyone hints or solutions?

      Here a test-page which give me same error during ispection of blue and red elements: https://jsfiddle.net/hbu35yvg/33/

      Thanks a lot.

    • Devtools does not work since install Microsoft Edge 42.17134.1.0. I’m getting this error on my server when trying to use devtools. ConnectionResetError: [WinError 10054] An existing connection was forcibly closed by the remote host

    • The Edge dev Tools stopped working everywhere. This is not conncected to Angular or anything. It’s not even working right here on Microsoft.com

      I made a small video where I just press F12 in this thread: https://youtu.be/Bp9vhZoI9N0

    • Is there anyone who found how to fix it, I am not able to debug my application in Edge

    • I am having the same issue. unfortunately non of the solutions above helped.
      I am using windows 10 1803, 17134.376 . My Edge version is Microsoft Edge 42.17134.1.0

    • This bug entry is only for the website manyvids.com -> DevTools -> Tab “Elements” -> crash
      (Other DevTool tabs are working)

      For other problems with DevTools create a new bug entry, but read this blog first:
      https://borncity.com/win/2018/11/07/windows-10-v1803-issues-with-update-kb4462933/

    • Richard S. 's Solution worked for me! Thanks!

    • I did try the power shell scrip with both open and closed edge, normal and admin user.
      It did not fix the issue.

    • The latest windows update, fix the issue for me. Thanks!

    You need to sign in to your Microsoft account to add a comment.

    Sign in