Internet Explorer IndexedDB Memory Leak

Fixed, not yet flighted Issue #7122372

Details

Author
Joe J.
Created
Apr 5, 2016
Privacy
This issue is public.
Found in
  • Internet Explorer
Reports
Reported by 4 people

Sign in to watch or report this issue.

Steps to reproduce

When setting and getting data in an IndexedDB store across multiple transactions memory usage climbs and does not go back down. The memory leak continues after refreshing the page. Eventually an UnknownError occurs when the memory usage gets to around 1200 - 1500 MB.
Network latency seems to have an effect on the leak. Hard drive speed has a bigger effect on the leak.
http://jjulik.com/IndexedDBMemoryLeak should be able to run forever without displaying an error message. This site stores some data in IndexedDB, pulls out the same data, and refreshes the page. The total amount of data stored is under 100 MB.
To reproduce the issue go to http://jjulik.com/IndexedDBMemoryLeak. Leave the page open and monitor the amount of memory that IE is using. It will start to climb. After a minute or 2, the website will display an UnknownError that is coming from IndexedDB.
The test stores a several large strings in an IndexedDB store, and gets the same strings out of the store. Afterwards it reloads the page. Other browsers (including Edge) are able to run this indefinitely.
The test seems to depend on network latency and hard drive speed. Try running it on a slower PC with an HDD. You should also be able to reproduce the issue by downloading http://jjulik.com/IndexedDBMemoryLeak/index.html and hosting it on your local machine.

Attachments

0 attachments

    Comments and activity

    • Microsoft Edge Team

      Changed Assigned To to “Venkat K.”

      Changed Assigned To to “Saty B.”

      Changed Status to “Confirmed”

      Changed Assigned To from “Saty B.” to “Qian Z.”

      Changed Assigned To from “Qian Z.” to “Ying C.”

      Changed Assigned To from “Ying C.” to “Sai S.”

      Changed Assigned To from “Sai S.” to “Xueping D.”

      Changed Status from “Confirmed” to “Fixed, not yet flighted”

    • It looks like the issue is fixed now. What version of IE will this fix be released in?

    • We do not have an estimate that we can provide but the fix will be rolled out ASAP.

      All the best,
      The MS Edge Team

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

    Sign in