Memory leak - IE Edge

Fixed Issue #8020622


Jun 28, 2016
This issue is public.
Found in
  • Microsoft Edge
  • Internet Explorer
Found in build #
Fixed in build #
Reported by 36 people

Sign in to watch or report this issue.

Steps to reproduce

Navigate to, open memory profiler, refresh the page.

Expected results: GC settles at around the same point each time
Actual results: significant growth in "Process memory usage", even though taking a heap snapshot shows the exact same object count across refreshes.


1 attachment

Comments and activity

  • Microsoft Edge Team

    Changed Assigned To to “Ibrahim O.”

  • Attached a minimal reproduction that leaks memory across refreshes.

  • Thank you for the feedback. Could you please re-attach your repro sample, seem like it failed before. If you will have trouble uploading here, you can also send us the link to your file that we can access.

    All the best,
    The MS Edge Team

  • Microsoft Edge Team

    Changed Assigned To to “Rico M.”

  • Ibrahim, I re-uploaded the reproduction.

  • Waiting for this issue to be resolved. We really need this !

  • This issue is also present in IE11

  • Hi this issue has been around for a while and is causing me massive issues. This issue is not in IE10 or below.

  • +1

  • this is affecting my sites too.

  • +1 Very interested too.

  • Microsoft Edge Team

    Changed Assigned To from “Rico M.” to “Riff J.”

  • This is also affecting our application, in both Edge and IE 11. Navigating around the application memory continues to grow even though each link is a new page. And as stated in this bug constant refreshing of the page will also grow the memory. Heap snapshots show small heaps but the overall memory usage continues to grow. Note when debugging I noticed the memory will always grow even on a page such as So to verify the issue I have been testing with the system monitor and watching the ram usage there for the tab. Closing the tab will free the memory.

    I will file an additional bug in case the two are separate but we are have a hard time determining what could be leaking the memory. We do not see this with any other browsers.

  • After reading comments from I downloaded the latest edge preview VM 39.14959.1000.0 from (I choose Microsoft Edge on Window 10 Preview 15.14959)

    It has fixed the memory leak on refresh of the page and general navigation for our application. Also notice the comment from IE developers on that issue, specifically “Please note that we are not working on IE feature bugs any longer at this time unless they are security related.”

    It does not look like we can expect this to be resolved in IE11.

    Update on your demo: I just loaded your example in the preview vm, using only the task manager to check the memory usage and it does not appear to be leaking memory anymore. I verified that your zip demo was leaking in my old IE11 version so this issue will probably be closed once microsoft dev teams reply.

  • Microsoft Edge Team

    Changed Assigned To from “Riff J.” to “Jeff W.”

    Changed Status to “In code review”

    Changed Assigned To from “Jeff W.” to “Riff J.”

    Changed Status from “In code review” to “Fixed”

  • Regarding Brian’s recent comments, there was still at least one memory leak occurring in recent builds of Edge.  We’ve plugged this one too; look for the fix in an upcoming flight.  Thanks for the report!

  • We have a very large angular app and this has been a big issue for us in IE and now EDGE. Does an update get posted reflecting what preview build this may be in so we can verify it is the source of our problems?

  • This fix should be present in any Windows Insider build 15026+.  Please let us know if your app runs better on one of these builds!

  • Jeff,

    So we tested against 15042 and our angular app still does not appear to be behaving in Edge or in IE 11. In both applications, we are seeing a low memory heap snapshot but the memory usage in Task manager is huge. We even do a browser refresh and it does not recover. It is more problematic in IE 11 as it always runs as a 32 bit app for some reason and once it hits 1.5 GB it crashes. Any thoughts as to what we may be missing? It could be our code as well but since the heap does not show any objects we cannot determine what is holding the memory. Any thought would be appreciated.

    I have a screenshot but I don’t see any way to attach it to the issue.


  • Rats, I’m sorry to hear that. :(

    Please open a new bug in our issue tracker (blue button in the upper-right area of this page), and post the number here once the bug is created so I can make sure it gets categorized correctly.  Please also include repro steps to your app, so that we can properly investigate.  Thank you!

  • I am going to have to figure out how to get you something reproducible. Our app is not publicly available/accessible. I’ll see if I can plunker something up that you may be able to use to track it down. Thanks!

  • I added a new issue #11106982. I accidentally marked it as private, I did not mean it to be, you can open up to the public.


  • Any news on this issue? I have the same problem on my large Angular application
    The link to #11106982 does not work :(

  • @Michael L: The link doesn’t work. Any news on that topic? We’re having the same exact issue with our large Angular application.

  • Oops, apologies for not getting back to this bug earlier.  I’ll try to get #11106982 opened up to the public.  The team that took an opening look at that bug noted that the leak is observed only when devtools is active, and so the bug is presently waiting for that team to take a look.

    Julien/Lupo, if your observed leaks occur only with devtools open, please wait for that bug to be made public.  If you can observe the leak without ever launching devtools, please open a new issue, so that it can be tracked as a separate issue.  Thank you!

  • #11106982 is now public.

  • Any updates on this issue?

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

Sign in