ABandonment- edgehtml.dll!CDocument։։item, Opening Window from Timeout Causes Crash

Fixed, flighted Issue #8494143


Jonathan S.
Aug 15, 2016
This issue is public.
Found in
  • Microsoft Edge
Found in build #
Reported by 9 people

Sign in to watch or report this issue.

Steps to reproduce

Opening a new window from within setTimeout will crash the new tab, as well as the tab for the parent document. Removal of setTimeout results in no crashes.

Test here: https://jsfiddle.net/jonathansampson/35rL2bgs/


0 attachments

    Comments and activity

    • Microsoft Edge Team

      Changed Steps to Reproduce

      Changed Steps to Reproduce

      Changed Steps to Reproduce

      Changed Steps to Reproduce

    • "Me too"… It took me 5-6 tries before it seemed to actually crash, although it didn’t bring up Bing, it just looked like a blank tab. Finally it caused the JSFiddle tab to error, too.

    • The first execution, the tab ‘crashed’ but recovered. Immediate second execution did the same, but 2nd time instead of recovering, got the “This page is having a problem loading” error.

    • Just tried on my Lumia 950XL. Did not seem to crash, but even though it looked fine, the tab was locked solid. Was able to switch to other tabs, only the one was locked up.

    • Reproduce this on Desktop, but not on Mobile :)

    • Microsoft Edge Team

      Changed Assigned To to “Travis L.”

      Changed Assigned To from “Travis L.” to “Adam B.”

      Changed Status to “Confirmed”

      Changed Assigned To from “Adam B.” to “Arron E.”

      Changed Title from “Opening Window from Timeout Causes Crash” to “ABandonment- edgehtml.dll!CDocument։։item, Opening Window from Timeout Causes Crash”

      Changed Assigned To from “Arron E.” to “Aparna P.”

      Changed Assigned To from “Aparna P.” to “Daniel C.”

      Changed Status from “Confirmed” to “In progress”

      Changed Status from “In progress” to “Fixed, flighted”

    • 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 Insider Preview build.

      Best Wishes,
      The MS Edge Team

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

    Sign in