Memory Leak issue in IE11 using ExtJS 4.2.1

[PankajG]

Memory Leak issue in IE11 using ExtJS 4.2.1

Hello Sencha Support Team,

I am building an application using ExtJS 4.2.1. It includes several components and around 10,000 records (buffered rendering). It works good in Chrome but IE sucks. In IE11, memory is not reclaimed after i close that display or refresh it resuling in overall system issue. I have tried using destory function and other workouts but it didn't helped a lot in IE.

It seems this is framework issue and is fixed in ExtJS 6.x but can we get a patch for this version since our application is already stable and we don't have time to upgrade and fix other issues.

Thanks
Pankaj

[Gary Schlosberg]

Thanks for the report. Officially, Ext JS 4.2.2 was the first version to support IE11. Do you have a test case which reproduces this issue?
https://fiddle.sencha.com/#home

[PankajG]

This issue can be seen in IE10 too. In Chrome, we are able to reclaim 100% memory but not in IE. It looks like an issue with iframes and unfortunately large majority of our customers insist on using IE10 and IE11.
If we leave application idle for few hours, memory goes extremely high since we push real time data in store. Having this real time updates on high frequency, application is not responsive. Also, there is memory leak when we refresh displays again and again.
We are explicitly destroying store and all other widgets used in the display during closing.

[Gary Schlosberg]

Are you able to post a test case which reproduces this memory leak?
https://fiddle.sencha.com/#home