We have used the grid in the server mode to display a minimum of 200 records and a maximum of 6000 records at a time. We have implemented paging, sorting, editing and inserting functionalities in the grid. The datasource to the grid is a dataset, which changes often in our application. Since we are using Server mode of the grid, for each operation, we hit the server and load the grid again. We are facing some problems in our application wherein we are getting 'Out of memory' exception. From our analysis, we found that this exception DOES NOT occur when we use the CLIENT MODE or the INTERMEDIATE MODE of the grid. We also found that whenever a dataset is assigned to the grid, the system memory increases tremendously. We presumed that the memory allocated to the grid is not getting released whenever a new datasource is assigned to it. We have to use Server mode of the grid to meet our application requirements, but it is posing a serious problem due to this memory issue.
Can you please do an analysis of this problem, and let us know, if in anyway we can overcome this problem? Thanks. Praveen.
Steps to Reproduce:
- Select the mode as 'Server-side mode(10000 records)' in the databindings page
- Open the task Manager. Click on processes and select aspnet_wp.exe
- Do paging and sorting in the grid.
- You can note that for each operation the Mem usage increase by a minimum of 3 MB and a maximum of 10 MB
- Within few minutes of operation on the grid, the memory usage, suppose it was 90 MB when it started, would have been 140 MB.
I forgot to mention that to test whether this problem is due to our code or our way of handling the grid, we used the demo application provided by you when we installed the grid. We tested the DataBinding' project which is in "\Developer Express .NET v6.1\Demos\ASPxGrid\CS\ASPxGridDemos\DataBinding" directory. The same memory problem occured where we able to see the memory rise tremendously whenever the datasource is changed or whenever we hit the server(like Paging, sorting)
We have not been informed of such problems so far. Please provide more information on how to replicate the problem. If it does occur with the DataBindings page of the ASPxGrid's demo, please add the precise steps to the "Steps to Reproduce" section of the report. This will help us diagnose the cause of the problem precisely.
Thanks,
Serge
Steps to reproduce
Can you please let me know the status of this issue?! We need the solution ASAP for our project.
Thanks,
Praveen
Dear Praveen,
Sorry for the delay, but we definitely need more time. The problem looks rather complex and we should perform some tests to clear up the situation. Please keep tracking. We will let you know once we have any news on this subject.
Thanks,
Serge
Sorry for the delay in responding. It has taken us some time to perform additional tests. As we can see, the problem is caused by the ASP.NET itself … it does work in such a manner. To understand this, we have created a similar sample with the standard DataGrid and we do see the same results - the memory usage increases on every postback. Though it is lower in comparison to the ASPxGrid, it is well explained by the fact that our Grid has a more complex server-side structure and creates more objects on the server.
Thanks,
Serge