ApplicationFrameHost to get stuck by using WebDriver and Edge

Not reproducible Issue #7326102


illy M.
Apr 25, 2016
This issue is public.
Found in
  • Microsoft Edge
Found in build #
Reported by 1 person

Sign in to watch or report this issue.

Steps to reproduce

After having the problem:
I updated windows to Build 14328 and WebDriver to Build 14316
Now I have a new additional problem (With the same setup) that after a few hours the Driver will timeout like before
But now when I connect to the RDP session the problem is not solved and the Edge Processes are in Running state but the Edge UI will not be visible
If I kill the Edge Processes and start Edge again it will start but again the UI will not show and any other Windows 10 app will not show either.
It can be workaround by killing the Process ApplicationFrameHost.exe
So its looks like that in the now version WebDriver cusses Edge to cusses ApplicationFrameHost to get stuck


Comments and activity

  • Microsoft Edge Team

    Changed Assigned To to “Brad E.”

  • Please try upgrading Win 10 to the latest Insider build: 14342 and see if this helps. If not please update this feedback so we can investigate. 

  • Tested it on build: 14342
    It was not fixed

  • Microsoft Edge Team

    Changed Assigned To to “Mara P.”

    Changed Status to “Not reproducible”

  • Typically the build of the server and the build of Windows should match. Please try this with 14393 WebDriver and the 14393 update of Windows 10 (the anniversary update). I’m currently not repro’ing this with the latest release.

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

Sign in