31 Aug 2011 8:35 AM #1
Possible memory leak with GridPanel and Store
Ext version tested:
- Ext 3.0.3
- Ext 3.3.2
- Ext 3.4.0
- only default ext-all.css
- Chrome 10
- Chrome 12
- Win 7 x64
- WinXP Pro
- There is a definite memory increase when using GridPanel with a store. Every time the store is reloaded and grid is rendered, the browser consumes more memory and it does not seem to free it. Best example is IE, which can consume over 1GB and crash within 30 minutes using the attached code.
Working code is attached. Unzip it into ext/examples
Steps to reproduce the problem:
- Open Click on Autorefresh button
- Observe memory consumption using e.g. sieve or Sysinternals Process Explorer
- Stable memory footprint
- Browser starts consuming memory until it crashes
- not provided
26 Oct 2011 9:45 PM #2
I'm seeing this with EXT JS 4.0.7 as well.. basically calling store.load() refreshes the Grid, and the memory keeps being used (up to 1GB before the browser dies): IE + Firefox 5
27 Oct 2011 5:58 AM #3
Sencha Devs, have you gotten anywhere with this one? I suspect there may actually be two issues, one with record id's and another with reader. And yes, it's still present in Ext JS 4.x.
27 Oct 2011 6:45 AM #4
29 Dec 2011 9:39 PM #5
Does it also happen when using "reload" method instead of "load" ?Extensions:
Ext.ux.menu.StoreMenu - Ajax Store as menu-item config
Extended Window - Aero Shadows, nested grayscaled modal windows
Ext.ux.plugin.triggerfieldTooltip (for Comboboxes, Datefields...)
23 May 2012 2:28 AM #6
We are facing the same issue. It would be great to have any answer from ExtJS team.
24 Jul 2012 10:40 AM #7
Has anyone heard from Sencha regarding this? It seems completely out of line that they're not even acknowledging it. There seems to be a similar leak in Sencha Touch that was fixed, but nothing has been done to even address the leak in ExtJS.
24 Jul 2012 3:56 PM #8
1 Aug 2012 1:20 PM #9
Hi All -
First off, apologies for the long delay in replying. We are looking into this issue now that we have some cycles with 4.1.1 and 3.4.1 having been released.
We will update you on whether or not we can reproduce it and if there are DOM leaks going on. If there are not, it is possible that it is a browser JS issue.
For IE, has anyone tried the (IE proprietary) CollectGarbage method to see if it helps?
2 Aug 2012 4:25 AM #10
Thanks for the heads up. My team hasn't tried the new IE CollectGarbage methods.