It looks like this bug is currently a problem in the latest version as well. The developers are working hard trying to isolate and fix it, but as I'm sure many of you have come to find, javascript memory leaks are an absolute nightmare to track. I'm keeping my fingers crossed that we'll have a solution in the next week or 2.

Tony,

 Thanks for taking the time out of your day to address this problem.  I have my fingers and toes crossed.

Cheers

Patrick

Last I heard (yesterday), the dev team had isolated the problem and had a potential fix.  Be sure that you've reported this to our support team so that you'll get automatically notified when a fix is available.

-Tony

Hi!

 Any news on this fix?

I'm experiencing the same problem. Is this perhaps solved in the 7.3 release?

 regards,

 Kjetil

Hi Kiran,

Did anything come of your support case? We are seeing the exact issues you are describing with 2010.3 release (utilizing mainly the non-akido "Ultra" controls... except modal window).

Hi Tony,

We are (using Infragistics2 v.7.3) facing exactly same problem. We are using fixed number of iframes in div tabs and as we click through those tabs iframes will be targetted to different pages with infragistics webgrid, webcalendar etc controls. Each time we switch through tabs IE process memory increases depending on number of webgrids in that page. This memory never goes down and reaches up till 800MB+ and system stops responding. Client side page unload event is definately firing up in our case because we have a clientside event firing that shows waiting gif image on page unload. So I dont understand why webgrid is not disposing when we switch through tabs. We are using setTargetUrl method to assign different addresses to iframes which is equal to setting IFRAME'S  source to about:blank (as per your suggetion).

Is there any client side dispose event for webgrids and other infragistics controls to free up when page is unloaded, or is there any way to see whether the wegrids are unloading while page is unloaded.

- Kiran

IFrames (especially dynamically created IFrames) can be very tricky when it comes to memory management.  Any objects created inside of the IFrame will use up memory.  When you remove the IFrame element from your page, it's not unloading the page that was loaded inside of the iframe - it's simply detaching the element from the DOM.  The WebGrid listens to the page_unload event and goes through it's own dispose method which is used to 'free' up memory that IE would otherwise neglect to collect.  It sounds like you're causing the objects to get lost by detaching the IFrame element from the document, without the grid first being disposed. 

My suggestion would be to manually unload your page.  Try setting the IFrame's source to about:blank rather than BLOCKED SCRIPTreturn false. 

The modal popup may also play a role in this as well, though I don't know the code well enough to be sure. 

I'm going to send a note to our docs team (they own the online help) and notify them of the possible memory leak.  Thanks for pointing that out.  I'll let you know if/when they figure out what caused it. 

-Tony

 Hi

We found memory leaks in UltrawebGrid control, Japanese Version - NetAdvantage for .Net (Jp) 2007 Volume 1 CLR 2.0 [simple vanilla webgrid without any client side events].

Herewith I attached a sample webApp [http://ko.infragistics.com/TestProjectUploads/ModalTest331200843010468.zip] and my test procedure to repro the bug . I would appreciate your immediate help to get away this memory leak because it is stopping us to release our application in to the production environment. 

Steps to Reproduce:

S/W Requirements:
1.    Visual Studio Web Developer Express / Visual Studio 2005
2.    ASP.NET AJAX Extensions 1.0
3.    AJAX Control Toolkit (Version 1.0.20229)
4.    NetAdvantage for .Net (Jp) 2007 Volume 1 CLR 2.0
5.    IE 6.0.2900.2180
6.     JavaScript Memory Leak detector http://blogs.msdn.com/gpde/pages/javascript-memory-leak-detector.aspx

Setup:
1.    Create an asp.Net C# WeSite as "Modaltest" in Visual Studio.Net2.0
2.    Unzip the web Application in to the "Modaltest" path
3.    Start the web Application

Test Procedure:
1.    The Sample application has got a default (default.aspx) page with one button and a dropdown list to choose Ultrawebgrid control [or] asp.Net gridview control
2.    Upon Click on the button, I am loading an Iframe dynamically with data grid (UltrawebGrid/gridview based on the selection) in it in a modalpopup (ASP.NET Ajax Control)
3.    I used JavaScript Memory Leak detector http://blogs.msdn.com/gpde/pages/javascript-memory-leak-detector.aspx and simultaneously monitored memory used by the IE in the performance Monitor.
4.    I found the amount of memory used by the IE keeps on increasing between 10-13 MB for each button clicks if UltrawebGrid is selected from the list (I.e. loading UltrawebGrid inside the dynamic Iframe)
Note: Iframe dynamically created during button click and destroyed during cancel/Ok buttons of the modal dialog
But if Microsoft gridview is selected (I.e. loading ASP.NET gridview control inside the dynamic Iframe), the amount of memory usage is consistent between each button clicks!

I have tested your Netadvantage online help webpage for such memory leak http://help.infragistics.com/NetAdvantage/NET/2007.1/CLR1.x/
Because some of our web pages have got similar functionality like Netadvantage online help i.e. search results in the Frame. Surprisingly I found that the amount of memory used by the IE keeps on increasing for each Search (Go Button) click!

 I highly appreciate your help.

Thanks and regards,
Senthilnathan Karuppaiah