We have a web application based on the Google Maps JS API which causes IE11's process memory usage to grow despite there being no apparent JS heap leaks reported by IE11's memory profiler.
We have created a self-contained test page which simulates some of the behaviours of the application and demonstrates the problem. We have a test page and does the following once the 'start' button is clicked:
* initialises a Google Map
* performs rapid marker movements on the map (simulating lightning strikes)
* plays a sound for each marker movement using Howler.js
* performs frequent AJAX requests to back-end a) JSON and; b) XML end points used by the application using jQuery
I can provide this test page on request, but prefer to keep it private for now.
In summary, there is no observable JS heap leak but the process memory increases until the browser is unable to operate normally. The process memory follows the same pattern when the test is run without opening dev tools.
Aspects of the test may be disabled by commenting out the relevant lines in the start() method and reloading the page. Our tests thus far have shown that the marker movements and sounds result in the most rapid increases however the process memory still grows when these are disabled.
I am happy to pay for someone at Microsoft / community to look into this.
Regards,
SH