Memory leaks of Active Widgets !!


I have a machine with 3.2 GHz processor with 2 GB RAM

When I open the web page with Active Widget grid, the browser takes about 10.5 MB of memory to render the full content with grid.

My Grid is abt 22x24 (rowXcol) in size and some columns are AW.Templates.Link and AW.Templates.Checkbox based.The grid has customised coloring for header and footer.
I have a preference screen through which I can change the order of columns on grid,apply some custom sort column and save the preferences to server as well as directly applying the changes to client without making a page refresh().

Each time I open the preference screen and modify the grid additional 0.5 MB gets allocated and this not recollected.

Can anyone suggest me whats the issue ? Or it is a Memory leak with ActiveWidgets ?
Vikramaditya Garg
Vikramaditya Garg
September 5,
I would suggest to check first if it is related to opening/closing the preference screen.
Alex (ActiveWidgets)
September 5,
Hi Alex,

I have checked the memory graph when preferences screen is opened and closed and its absolutely fine.

Abt 5-8 MB of memory gets lost when we try to remodify that grid without any page refresh.We cannot do page refresh becoz of our business requirements.

We are now trying to remove older grid and create new grid on the older one .Can that would be helpful for us to prevent memory leak?

Actually our preference screen sends the changed preferences using AJAX to the server side and we just modify the grid at client side without doing page refresh.We are using AJAX in async mode and AJAX save at the server side hardly takes more than 125 ms.The remodification at the client takes about 2.5 seconds after which browser keeps on processing for another 3 seconds for garbage collection activities .We need to save these 3 seconds in order to show better performance.
Can you suggest some techniques for using ActiveWidgets which can help us to prevent Memory Leaks?

Vikramaditya Garg
Vikramaditya Garg
September 6,

This topic is archived.

See also:

Back to support forum