Memory leak in Edge and Internet Explorer 11

Confirmed Issue #14540533 • Assigned to Zoey W.

Details

Author
Jiri B.
Created
Nov 6, 2017
Privacy
This issue is public.
Found in
  • Microsoft Edge
  • Internet Explorer
Reports
Reported by 1 person

Sign in to watch or report this issue.

Steps to reproduce

This issue is similar to #8020622. However it is not fixed yet, I have reproduced it on Insider Preview build 16299 in both Edge (41.16299.15.0) and Internet Explorer 11 (11.15.16299.0).

The issue is that when using our web application, the memory usage of Edge and IE11 processes constantly grows. With IE11 and its 32-bit processes this means that the browser will crash frequently - as soon as the process size reaches ~1.5GB.

To reproduce it you can use our publicly available demo server: open demo and login using these credentials:

Username: tomas.soukup@siemens.com
Password: nq4tasjt

When you open this page in Edge/IE11 the browser processes will take ~220MB.
When you use the refresh button in the top right corner of the screen (so this is NOT the refresh of the whole page), the memory will start to grow. After about 20 refreshes the browser processes will take more than 500MB.

This memory growth is there even when not using the developer tools. We think that this is not a JavaScript leak, because the developer tools in Edge (the memory analysis does not work for us in IE11), when used, show no significant memory growth.
In Chrome and Firefox, the memory consumption is lower and does not grow over time.

This behavior of Edge and IE11 is very problematic for our customers and we need to recommend to use other browsers.

Attachments

0 attachments

    Comments and activity

    • Microsoft Edge 41.17025.1000.0
      I can confirm this leak using the steps noted above. I’ve also duplicated this issue generally browsing the internet using a wide variety of business, social and general sites. For the first time in 10 years, I like the features of Edge. This is type of flaw is unprofessional and demonstrates a basic lack of care and concern by MS for their users.

      Sadly it goes to the core of fundamental problems with MS’ corporate culture and it’s lack of focus on it’s clients. I get that it’s a big organization, but that’s when better companies focus even more on consistently delivering the best products to their clients.

      Google doesn’t get a pass either, their arrogance is almost astonishing sometimes. but at least I can use Chrome all day and worry little about security or memory leaks.

    • Microsoft Edge Team

      Changed Assigned To to “James M.”

    • Hello,

      Thank you for providing this information about the issue. After thorough testing, we are unable to reproduce this problem in Edge with the information at hand. Specifically, once logged in the URL https://almdemo.polarion.com/polarion/#/project/Microsoft/wiki/Requirements/ says this page does not exist and offers 4 options to proceed. We chose the first option and tried refreshing that page over and over as described. We also tried refreshing the home page the same way but never saw the problem.

      Please update this case when you can provide more details, such as screenshots and more detailed repro steps.

      Best Wishes,
      The MS Edge Team

    • Hello,
      I think you have used wrong URL, I have just reproduced it on:

      https://almdemo.polarion.com/polarion/#/project/Microsoft/wiki/Requirements/E-Library%202250

      If you will still have problem to reproduce it, I can record a video.
      Thank you for taking a look on it

    • The instructions in the original post are correct and do work. It’s really troubling James M’s response notes he couldn’t “logon” to the test site. Perhaps there are corporate restrictions imposed on Microsoft employees/agents. Please escalate to a supervisor,

      Using the instructions in the original post, I can easily reproduce the memory leak. I love MS Edge (for the first time ever), but I can’t use it because of the memory leak.

    • Hello Jiri,

      I was using an incorrect URL; thank you for the clarification. We are investigating this issue now, and we will provide an update to this case when we have more progress.

      Best Wishes,
      The MS Edge Team

    • Microsoft Edge Team

      Changed Assigned To to “wprpprtri@microsoft.com”

      Changed Assigned To from “wprpprtri@microsoft.com” to “Zoey W.”

      Changed Status to “Confirmed”

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

    Sign in