Wait! Looks like we don't have enough information to add this to bug database. Please follow this template bug format
IE9 Memory Leak
IE9 Memory Leak
Ext version tested:Browser versions tested against:DOCTYPE tested against:Description:
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:
The result that was expected:
- Open the page (note the memory usage)
- Refresh the page (F5) several hundred times, and notice the memory usage gradually increase
The result that occurs instead:
- The memory is freed after each page refresh.
- Memory usage gradually increases and is not freed until the browser is closed.
Additional CSS used:Operating System:
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
<meta http-equiv="cache-control" content="no-cache" />
<meta http-equiv="pragma" content="no-cache" />
- Windows 7 Professional, Service Pack 1
Sencha - Senior Forum Manager
Have you tried with the latest release? 4.2.0 beta2?
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.
Ext JS Premium Member
But seriously, why the hell is this not hotfixed as some kind of 4.1.4?