Possible memory leak with GridPanel and Store

Hi Don,

Thanks for the answer!

Quote:

---

Originally Posted by dongryphon

For IE, has anyone tried the (IE proprietary) CollectGarbage method to see if it helps?

---

I just tried it with my test case: 5 columns, 30 records, reloading every 3 seconds, IE9.

~ 1 hour testing time increased memory from ~38000 KB to 63780 KB.

Then called CollectGarbage() on the console and it became 63144 KB. So, only ~600 KB off.

I call it several times more - no significant effect. Just a few bytes up and down.

So, I can say it doesn't help.

Quote:

---

Originally Posted by dongryphon

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.

---

Please note it is reproducible in Chrome, FireFox and IE. Unlikely it's a browser JS issue. Though anything is possible. In that case it would be great to report it to the browsers technical support.

Bump...this is a show stopper...

I create real-time reporting and monitoring applications using ExtJS, so it is crucial for me to fix this. As I suspected, there are two separate issues here:

1. ExtJS uses Douglas Crockford's implementation of JSON parser, which is the problem. I have swapped the parser for this one: http://code.google.com/p/json-sans-eval/ and that stopped the leaks.
Just include the above parser and patch ExtJS like this:

Code:

---

Ext.util.JSON.decode = jsonParse;
Ext.decode = jsonParse;

---

2. If your record id is autogenerated, it will leak.Configure your JsonReader.idProperty and make sure your id is unique. Autogenerated record id's are prefixed with 'ext-record'. This applies to all types of stores, not only JSON.

I was able to run my test case with the above modifications for 2 days without any leaks.
The same applies to ExtJS 4.x

Hope this will help.

This could prove to be very helpful information. But you make two very broad statements without any explanation. Can you please explain why it is that you feel that the Douglas Crockford implementation of JSON parse is the culprit, and why you think auto-generated IDs cause leaks?


Thanks

Unfortunately I don't have enough time to identify which code actually causes the leaks. I can only do my best to help all of us fixing this problem by providing test cases and a workaround without an explanation. Please verify my claims and correct me if they are wrong.

Hi Ext Team,

My whole application is build on the ExtJs API and now we are facing the same memory leak issue. We are working on lots of data and we present it on Grid using Data stores. When opening the same grid panel again and again, the browser memory keeps growing and becomes unresponsive after some time. I found this thread after searching for any solution. I did not see any last response with the issue to be fixed. Can you suggest any solution of the issue. It will be a great help.

Thanks,
Jitesh