I'm using UltraWebGrid and I can observe that the memory is not garbage collected even a few hours after the session is closed. Explicit 'Dispose' call doesn't work in my case. I override 'Dispose' method in the form which keeps a reference to an UltraWebGrid object:
public override void Dispose() { base.Dispose();
uwg.Dispose(); }
The reference seems to be still kept by the ScriptManager (as it can be seen in MemProfiler). I'm using UltraWebGrid 8.2. What shall I do to solve the problem?
Was this issue ever resolved? I've been googling around and found lots of reported incidents of this but alas no resoluition. I'm currently using version 9.2 of the Ultrawebgrid and at this time, it's not possible for us to move to another version of the grid or port the functionality to one of the newer WebDataGrids. Any suggestions anyone has will be welcomed.
No, I think it is still there, at least in 10.x. We mitigated the problem by restarting IIS once a day and enabling process recycling with memory thresholds.
Hello Chu,
There was essentially an issue where if an async postback occured too quickly (usually several postbacks in a row) on the parent UpdatePanel for a WebTab that client memory wouldn't get cleaned up correctly. This is resolved in the latest service release for NetAdvantage for 2012 Vol. 1, 2011 Vol. 2, and 2011 Vol. 1.
This service release is available under your account at the Infragistics Website. To download the service release, log in to ‘My IG’ and select ‘Keys & Downloads’. Select the NetAdvantage tab and then click on the product name. The available service releases should now be listed on the page underneath the tab control.
Please let me know if you have any further questions or concerns about this matter.
Chu,
I have created case CAS-87171-RZC9VX for you and linked the case to development issue 103982 for the memory leak with the WebDataGrid.
When the development issue is resolved, I will also update this thread again.
Hi Alan,
Yes, we are using Update Panel.
Regards,
Chu
bartond31,
If you are using the release of NetAdvantage 2009 Volume 2, then I would recommend upgrading the latest service release to see if that resolves the issue. I am making this suggestion because there was a memory leak caused by the implementation of GlobalCSSHelper which was part of the shared assembly and used by multiple controls.
blount,
If you are using NetAdvantage 2010 Volume 1, if you are seeing a memory leak it likely is due to a different cause and I would need more specific details to look into the issue.
Nguyen,
For your client side memory leak with the WebDataGrid, I have a colleague currently looking into an issue that is caused only when using an UpdatePanel. Are you using an UpdatePanel in your application?
Let me know if you have any questions with this matter.
Hi all,
We are having memory leak with WebDataGrid from 2011.1 also.
After each time open a WebTab that contains a WebDataGrid then close the tab, the memory that IE used is increased.
After 6 hours of using the application, the IE uses 1.6 GB of RAM.
Is there a way to dispose all objects from WebTab and WebGrid after close a Tab at Client side?
Here is how we currently close a tab:
--------------------
webTab.set_hidden(true);
webTab = null;
-------------------
Anyone have any solution - this is preventing us to finish up the project.
Thanks,