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.
Thanks for your reply Blount. We've had to do the same, re-cycling the process pool of the website. Infragistics is there a solution??
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,
Chu