Steps to reproduce
- View https://samples.dundas.com/Dashboard/c397551a-e1f0-48e2-bb22-fa0def388063?e=false&vo=viewonly
- Lock or disconnect from the Windows session (recommended)
- Wait for an extended period of time without logging back in (recommended)
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.
The attached graph tracks only “working set” by mistake, but private bytes and working set have been similar.
Comments and activity
- Microsoft Edge Team
Changed Assigned To to “Steven K.”
Have you tested this in a recent Insider’s release? My testing did not reproduce this memory leak.
Appreciate the help,
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.