Memory leak viewing page with regular updates

Issue #16372400 • Assigned to Steven K.

Details

Author
Jamie C.
Created
Mar 13, 2018
Privacy
This issue is public.
Found in
  • Microsoft Edge
  • Internet Explorer
Found in build #
41.16299
Reports
Reported by 1 person

Sign in to watch or report this issue.

Steps to reproduce

  1. View https://samples.dundas.com/Dashboard/c397551a-e1f0-48e2-bb22-fa0def388063?e=false&vo=viewonly
  2. Lock or disconnect from the Windows session (recommended)
  3. Wait for an extended period of time without logging back in (recommended)

Memory consumption by one Edge process increases at a roughly constant rate continually, for example an average of 5.6MB/hour, from 392MB to 1,179MB over 140 hours. This memory consumption may decrease sharply but only at the moment a user logs back to view the page if following steps 2-3. Memory snapshots have shown JavaScript bytes and object counts hovering near the same numbers over time, with bytes going both up and down by a few hundred kilobytes. We cannot reproduce results like this in Chrome.

Steps 2-3 may not be necessary, but the results may be different or less reliable without them: we have seen memory consumption going up and down, or going up less sharply.

This may be similar to #14540533. The problem affects our pages where JavaScript makes regular web requests for data and updates the page’s DOM. IE11 will become unresponsive after a shorter time.

The attached graph tracks only “working set” by mistake, but private bytes and working set have been similar.

Attachments

Comments and activity

  • Microsoft Edge Team

    Changed Assigned To to “Steven K.”

  • Hi Jamie,

    Have you tested this in a recent Insider’s release?  My testing did not reproduce this memory leak.

    Appreciate the help,

    Steve

  • Sorry for the delay. It’s been difficult to confirm given that a single test should take multiple days, but testing with build 17738 so far showed a much smaller increase of 1MB/hour of increased consumption followed by a drop, which could amount to the issue being fixed. We are still testing.

  • With build 17738, a test over almost 8 days still seems to show a steady increase in consumption that never ends as long as the workstation and/or session remains locked (DataCollector02.gif attached). The rate of increase now seems just over 1MB/hr, so it’s possible the problem is smaller now, otherwise maybe the specific rate can vary. Chrome still shows only steady memory consumption for the same page.

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

Sign in