Possible memory leak with GridPanel and Store

Ext version tested:

• Ext 3.0.3
• Ext 3.3.2
• Ext 3.4.0

Adapter used:

• ext

css used:

• only default ext-all.css

Browser versions tested against:

• IE8
• IE9
• FF4.0.1
• FF6.0.1
• Chrome 10
• Chrome 12

Operating System:

• Win 7 x64
• WinXP Pro

Description:

• 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.

Test Case:
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

The result that was expected:

• Stable memory footprint

The result that occurs instead:

• Browser starts consuming memory until it crashes

Debugging already done:

• none

Possible fix:

• not provided

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

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.

No replies yet, but I did find out that if I stopped doing the "load", the memory eventually did go down a bit. The bad news means that it might just be a standard javascript/browser/os interaction problem!

Does it also happen when using "reload" method instead of "load" ?

We are facing the same issue. It would be great to have any answer from ExtJS team.

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.

Quote:

---

Originally Posted by dcohn

Has anyone heard from Sencha regarding this?

---

No, I does not. Unfortunately.

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?

Thanks for the heads up. My team hasn't tried the new IE CollectGarbage methods.