Memory Leak when Using Ext4 Sandbox and IFrame

Memory Leak when Using Ext4 Sandbox and IFrame

I posted this in the general forums, but haven't gotten a response. Hopefully I'll get some more help here

Hi Everyone,

We have a dashboard system for stats at my work and each dashboard is in an iframe (due to legacy support). So each time a person using our system wants to look at their stats, the iframe is refreshed and it loads up many Ext.grids and Flash charts all arranged in many patterns. We wanted to slowly cut over our charting system to Ext4, with the older grids still remaining on Ext3 for a time. Right after the initial release of including the Ext4 sandbox library in our dashboard system, we started getting many out of memory errors. After some time tracking down the source we created a simple scenario which can consistently cause a large memory leak.

We can't figure out why this is causing a memory leak, we have tried many methods of destroying the iframe and the objects within. I'm wondering if anyone else can provide insight into this memory leak.

Our best guess is that somehow the Ext4 sandbox library is creating objects on the parent frame (instead of its own window scope) due to a coding mistake which would only show up in a situation like this.

We have a dashboard system for stats at my work and each dashboard is in an iframe (due to legacy support). So each time a person using our system wants to look at their stats, the iframe is refreshed and it loads up many Ext.grids and Flash charts all arranged in many patterns. We wanted to slowly cut over our charting system to Ext4, with the older grids still remaining on Ext3 for a time. Right after the initial release of including the Ext4 sandbox library in our dashboard system, we started getting many out of memory errors. After some time tracking down the source we created a simple scenario which can consistently cause a large memory leak.

Why hasn't this been looked at?

Why hasn't this been looked at?

This is a crippling issue for us as well, I'm really astonished such a roadblock has gone unfixed for over a year now. The issue still stands with even the 4.2.1.744 beta. Any iframes created never release their memory back. Open a few extra tabs with an iframe in them and you'll see increments of 20-100MB each time, staying there until IE8 is closed.

I didn't know whether to start a new thread or to bring back the old one, but this saved me from creating an identical example. In our case, simply loading an iframe with a viewPanel, then closing the parent window causes the same issue.

Last edited by m0r14rty; 9 May 2013 at 2:00 PM.
Reason: added another link to same issue