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.
26 Jun 2014 6:08 AM #7
Has anyone tried to apply suggestions from post #13?
27 Jun 2014 2:46 AM #8
The suggestions from post #13 aren´t relevant for me because I have an xml store and all rows have an id. The problem of high increasing memory still exists.
15 Aug 2014 2:14 AM #9
I have the same problem with a memory leak in a REST store in both v4 and v5.
I create a v5 app using sencha cmd, added a REST store and a dynamic task in which I load/reload the store every 1 second, nothing else going on, just the load, but in less than a day both FF and chrome will crash because of the memory leak.
It looked like a problem with the data.proxy.Rest reader, but it was to difficult to work out exactly what was leaking. In the end I decided to bypass the data.proxy.Rest reader and write my own simple XMLHttpRequest handler, manually loading the response into the store.
This solved the leak in the store but now I have a chart linked to another store that is updating every 4 seconds and the chart seems to be leaking memory as well.
Does everything in EXT leak? Any attempt at writing a serious SPA that's intended to run continually seems doomed to fail.
16 Aug 2014 8:17 PM #10