Memory Leak IE/Edge with Angular App when refreshing while using F12

Fixed, not yet flighted Issue #11106982

Details

Author
Michael L.
Created
Feb 28, 2017
Privacy
This issue is public.
Found in
  • Microsoft Edge
  • Internet Explorer
Found in build #
15.15042
Reports
Reported by 2 people

Sign in to watch or report this issue.

Steps to reproduce

This issue is similar to #8020622. We are seeing memory leaks in our Angular JS application.

Steps to Reproduce:

In Edge build 15042:

  1. Navigate to this plnkr example
  2. When page loads open Developers Tools F12
  3. Open Task Manager to monitor processes Private Byte usage
  4. Note Starting memory usage (in screenshot example it is ~55MB)
  5. Take Snapshot to note memory usage. Write it down as it will be removed in one of the steps. (3.17MB in my example)
  6. Click on the Route 1 Link at the top. This will load a large table. This may take a little bit so wait until data appears.
  7. Click on the Home link. This will clear the page and remove the data structures.
  8. Again, click on the Route 1 Link at the top. This will load a large table. This may take a little bit so wait until data appears.
  9. Again, click on the Home link. This will clear the page and remove the data structures.
  10. Click on the browser reload button. Note memory usage when it is complete. You will see a drop but it will not go down to original state.

In my example, we gained 165MB of memory usage.

Similar behaviors occur in IE as well and it tends to be worse in IE.

Let me know if you need more information.

Thanks,
Mike

Attachments

Comments and activity

  • This issue can be made public. It was accidentally marked as private.

  • Microsoft Edge Team

    Changed Assigned To to “Rico M.”

    Changed Assigned To from “Rico M.” to “Todd R.”

    Changed Status to “Confirmed”

    Changed Title from “Memory Leak IE/Edge with Angular App” to “Memory Leak IE/Edge with Angular App when refreshing while using F12”

    Changed Assigned To from “Todd R.” to “Mike J.”

    Changed Status from “Confirmed”

  • I was able to reproduce the reported memory leak, but only when F12 was open. Thanks for the bug report!

  • Microsoft Edge Team

    Changed Status to “Confirmed”

    Changed Assigned To from “Mike J.” to “Brandon W.”

    Changed Assigned To from “Brandon W.” to “Yong C.”

  • Making bug public (it was accidentally privately reported).

  • Microsoft Edge Team

    Changed Status from “Confirmed” to “Fixed”

  • Worth noting that I see a similar leak when refreshing this very page with dev tools open in ie11.

    @yong does your Fixed status mean that this is no longer an issue across all maintained ie & edge browsers? Also, do we have to wait for edge users to upgrade their windows system to see the fix?

  • Hello,

    Thank you for providing this information about the issue. We are pleased to report this feature is fixed in Edge and will be available in an upcoming Insider Preview build.

    Best Wishes,
    The MS Edge Team

  • Microsoft Edge Team

    Changed Status from “Fixed” to “Fixed, not yet flighted”

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

Sign in