Memory increase when setting url repeatedly to the src attribute of img element

By design Issue #14991501

Details

Created
Dec 7, 2017
Privacy
This issue is public.
Found in
  • Microsoft Edge
Reports
Reported by 1 person

Sign in to watch or report this issue.

Steps to reproduce

Repro step:
Open attached html file with Microsoft Edge.

Expected Result:
Memory does not increase.

Actual Result:
Memory will increase.

Addtional information:
This problem occurs on Windows 10 v1703 and v1709.
It is not verified with Windows 10 v1607.

Attachments

1 attachment

Comments and activity

  • Microsoft Edge Team

    Changed Assigned To to “James M.”

    Changed Assigned To to “wprpprtri@microsoft.com”

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

    Changed Status to “Confirmed”

    Changed Status from “Confirmed” to “By design”

  • Thank you for your feedback. The allocated memory is cleaned up by the garbage collector within a short order of time. Our testing has shown that this behaviour occurs on Firefox and Chrome as well, albeit within their respective compositor processes. This area may be a target for future optimization, as we work to reduce memory consumption within Edge. This feedback also helped us to isolate a reproduction scenario for a similar issue.

    As this is expected behaviour, we are closing this item as By Design.

  • Microsoft Edge Team

    Changed Assigned To to “Zoey W.”

    Changed Status from “By design”

  • I took a look at this with another engineer, and they pointed out that the total commit was around 450 megabytes for this scenario. Although private working set was around 60 megabytes, the commit was higher than expected.
    Reopening to take a closer look.

  • Microsoft Edge Team

    Changed Status to “Confirmed”

  • The memory usage observed is due to the image deduplication cache, which keeps a number of images in memory after their last usage to ensure that if the URL is requested again we will be prepared to serve them immediately.
    In response to this issue, we will be adding more monitoring for the behaviour of this cache to determine room for potential optimizations. As for this issue, I am closing it as By Design, as it is the intended behaviour of the existing cache.
    Our current belief is that images on most real-world webpages are smaller than this repro, and would have significantly less impact on memory, but this monitoring will allow us to verify this assumption.

  • Microsoft Edge Team

    Changed Status from “Confirmed” to “By design”

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

Sign in