5 Feb 2013 10:14 AM #1
IE9 Memory Leak
IE9 Memory Leak
Ext version tested:
- Ext 4.1.0
- <!DOCTYPE html>
Below is a simple page that demonstrates a memory leak in Internet Explorer version 9. On initial load, the page consumes approximately 51MB of memory. After hundreds of page refreshes (F5), the page consumes 78MB of memory.
The page simply loads the ExtJS library and display a div, but there is gradual memory leak accumulation after each page refresh. The memory is not freed until the browser is closed.
This issue appears to only affect Internet Explorer.
Steps to reproduce the problem:
- Open the page (note the memory usage)
- Refresh the page (F5) several hundred times, and notice the memory usage gradually increase
- The memory is freed after each page refresh.
- Memory usage gradually increases and is not freed until the browser is closed.
- Windows 7 Professional, Service Pack 1
5 Feb 2013 10:41 AM #2
- Join Date
- Mar 2007
- Gainesville, FL
- Vote Rating
Have you tried with the latest release? 4.2.0 beta2?Mitchell Simoens @SenchaMitch
Sencha Inc, Senior Software Engineer
Check out my GitHub, lots of nice things for Ext JS 4 and Sencha Touch 2
Think my support is good? Get more personalized support via a support subscription. https://www.sencha.com/store/
Need more help with your app? Hire Sencha Services firstname.lastname@example.org
Want to learn Sencha Touch 2? Check out Sencha Touch in Action that is in print!
When posting code, please use BBCode's CODE tags.
15 Feb 2013 8:34 AM #3
Tested against the latest beta, and the issue still exists. I should mention two important points that I discovered:
1) The issue does not occur in IE8, but affects IE9 only
2) The issue does not exist when the DOCTYPE is omitted
I've attached a graph of the memory usage below. As you can see, it takes a lot of refreshes (hundreds) before the pattern clearly emerges, much more than would be typical for any reasonable application. However, my concern is that the issue may be representative of deeper memory issues. It's also surprising that a page refresh would not reclaim all memory from the previous.
26 Feb 2013 12:04 AM #4