This page is having a problem loading (Edge 40.15048.0.0)

Issue #11235452 • Assigned to John-David D.


Ron G.
Mar 10, 2017
This issue is public.
Found in
  • Microsoft Edge
Found in build #
Reported by 2 people

Sign in to watch or report this issue.

Steps to reproduce

The version information we are working with is:
Windows 10 Home Insider Preview
Evaluation copy. Build 15048.rs2_release.170228-1522
Microsoft Edge 40.15048.0.0
Microsoft EdgeHTML 15.15048

When we load the room planner software, Edge tries a few times to load our in-browser application and then reports
This page is having a problem loading
We tried to load this page for you a few times, but there is still a problem with this site…

You can try this yourself using this URL within Edge 40.15048.0.0:

This problem does not occur in IE 11.0.15048.0 which ships with this Windows 10 Home Insider Preview Evaluation copy. Build 15048.rs2_release.170228-1522.

This loading problem is definitely a regression issue because it does not occur with the now current Windows 10 Microsoft Edge release 38.14393.0.0 EdgeHTML 14.14393 which ships with Windows 10, Version 1607 (OS Build 14393.693).

The problem does not occur with the other browsers, including Chrome, IE, Firefox, and the current production release of Edge 38.14393.0.0


0 attachments

    Comments and activity

    • As for the refresh it is not a scripted refresh but a crash in the edge process while attempting to load your page:

      Faulting application name: MicrosoftEdgeCP.exe,
      Faulting module name: edgehtml.dll
      Exception code: 0xc0000602
      Fault offset: 0x0000000000748f24
      Faulting process id: 0x4348
      Faulting application path: C:\Windows\SystemApps\Microsoft.MicrosoftEdge_8wekyb3d8bbwe\MicrosoftEdgeCP.exe
      Faulting module path: C:\WINDOWS\SYSTEM32\edgehtml.dll
      Faulting package-relative application ID: ContentProcess

      I hope you guys can address this bug in the next build. This is very important to us.

    • @Ron G: Please create a Feedback-Hub entry in the category “Microsoft Edge -> Browser crashes or stops working” so we can upvote and use the “Start capture” function.

      Microsoft Edge

      Stopped working

      ‎3/‎12/‎2017 8:10 AM

      Report sent

      Faulting Application Path: C:\Windows\SystemApps\Microsoft.MicrosoftEdge_8wekyb3d8bbwe\MicrosoftEdgeCP.exe

      Problem signature
      Problem Event Name: MoAppCrash
      Package Full Name: Microsoft.MicrosoftEdge_40.15055.0.0_neutral__8wekyb3d8bbwe
      Application Name: praid:ContentProcess
      Application Version: 11.0.15055.0
      Application Timestamp: 58bf6e30
      Fault Module Name: edgehtml.dll
      Fault Module Version: 11.0.15055.0
      Fault Module Timestamp: e7504fc8
      Exception Code: c0000602
      Exception Offset: 0000000000748f04
      OS Version: 10.0.15055.
      Locale ID: 1033
      Additional Information 1: a8b4
      Additional Information 2: a8b409d911f084b4c4ac1167888b46f8
      Additional Information 3: bb00
      Additional Information 4: bb00f5e867b3af99d98cddf403b20e9b

      Extra information about the problem
      Bucket ID: ff4fdd80c83c5d82ee4c813885c7a8dc (133472211792)

    • I have used the Feedback Hub app to report the problem which continues even after the very latest Insider Preview has been downloaded and installed: Build 15055.
      The title of my Feedback Hub submission is
      “Edge loads page a few times, then Faults” dated 3/12/2017
      and I have classified as you have requested: “Microsoft Edge -> Browser crashes or stops working”.
      I’ve attached a system monitoring file and screenshot.
      Thank you!

    • Microsoft Edge Team

      Changed Assigned To to “James M.”

      Changed Assigned To to “Rico M.”

      Changed Assigned To from “Rico M.” to “Lee H.”

      Changed Status to “Fixed”

    • In which version will we see the Fix? Can you identify the Windows 10 version number or the EdgeHTML version number?

      If you cannot identify the specific version, can you give some estimate like “after version XXX” or "after "?

    • Changed Status from “Fixed”

    • Can you please give some indication as to the version number or the date when the fix will become available?

    • Microsoft Edge Team

      Changed Assigned To to “James M.”

      Changed Status to “Fixed”

    • Hello,

      Thank you for providing this information about the issue. We are pleased to report this feature is fixed in Edge 15063 and is available in our latest Creator’s Update build.

      Best Wishes,
      The MS Edge Team

    • Changed Status from “Fixed”

    • Unfortunately, I am sure that this bug has NOT been fixed in Edge 15063. We have identified a software workaround and have implemented that in our application. Unfortunately there does not appear to have been a pertinent update to Edge that addresses this problem.

      If you are now testing using the prior submitted method of reproducing the problem, the problem will no longer occur because of the workaround we’ve implemented. Unfortunately, the bug still exists in Edge. We are simply avoiding it.

      When we have a moment, we will post another method that you may use to reproduce the problem.

    • Microsoft Edge Team

      Changed Assigned To to “James M.”

    • Hello,

      My apologies; I meant to communicate this feature is fixed in Edge 16176 and is available in our latest Insider Preview build.

      If you still find it is not already fixed in 16176, please do provide us with a sample webpage without the workaround so we can repro.

      Best Wishes,
      The MS Edge Team

    • Dear Microsoft Team,
      This problem has not been resolved in Microsoft Edge.
      The originally reported problem still exists. We’ve tested and confirmed this using Build 16176.rs_prerelease.170410-1642.
      We have implemented a workaround in our code that avoids the issue.
      As a result, the problem is no longer apparent when you use the URL

      We have now implemented a URL parameter that will effectively remove the workaround. To reproduce the original problem, using our original code (without the workaround) please use the URL

      Thank you for continuing to investigate this and work toward a solution.

    • Microsoft Edge Team

      Changed Assigned To to “John-David D.”

      Changed Status to “Confirmed”

    • Hi Ron!

      Would you share the details of the Edge workaround. Are you avoiding a specific API or feature set?

    • Please review the function uniquifyElems that reassigns svg elements with unique id codes.
      Search for string “roomplanConfiguration.skipEdgeWorkaround” to see the exact part of the code that needs to be skipped to be able to run in Edge.

      When your dev team is ready to tackle this, we are willing to put you in touch with our lead developer. We can help you with access to the source code, etc. Use the URL parameter debug=true to obtain the non-minified javascript.

      To contact us about this issue, please initiate your request by sending email to us at and include a reference to and mention my name, Ron Gordon, along with the appropriate non-public way to contact you.

    • Microsoft Edge Team

      Changed Status from “Confirmed” to “Fixed”

    • Thank you Ron! I’ve tested this issue on the latest insider preview and it seems to have been resolved. The site loads and operates with or without the workaround enabled now. If you find that the site is still having problems or run into other issues please let us know.

    • Changed Status from “Fixed”

    • John, would you please document what build you are referring to when you say that you’ve used the “LATEST” insider preview? Doesn’t that build have a specific number associated with it?

      I’ve tested it with the latest insider preview build that I have. I am on the Fast Ring. The latest insider build that I have access to through Windows Update is Version 1703 Windows Insider PReview 16215.1000. This build still exhibits the problem using the URL

      The page loads and reloads a few times and then gives up with the message:
      This page is having a problem loading
      We tried to load this page for you a few times, but there is still a problem with this site.

      Please reopen this issue as we have NOT been able to confirm that this problem has been fixed. Thank you! We appreciate your ongoing efforts to get this resolved satisfactorily.

    • Microsoft Edge Team

      Changed Assigned To to “John-David D.”

    • Ah I noticed I’m on an internal ring. I’ll keep an eye on it and report back when it makes it’s way to a public preview.

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

    Sign in