I have an asp.net website where few pages contain Telerik Reports. I found that the pages with the reports retains data in memory even after I move to a different page closing the previous one (it keeps summing up). Every time I run a report, 10-15 Mb are added-up and do not get released. I think this is a memory leak.
Attached the picture I got using Justtrace. The rump up is basically caused by reports getting opened/launched on different webpage, one at time (switching between pages). The long standstill situation of the memory at the higher value is basically no-activity on the website showing a page with the last report opened. As you can see the memory never gets released.
How can I free the memory once the report is rendered to avoid such issue?
1 Answer, 1 is accepted
answered on 15 Nov 2013, 08:36 AM
Generally Telerik Reporting is utilizing it's own Cache Management. Our cache management by default is set to Auto and in this mode an actual provider is chosen automatically according to the characteristics of the stored resource and the permissions granted to the application. In this way some of the cache is stored in the memory. This way the report viewers have fluent interactivity and better overall performance. Additionally the life cycle of the cached object (report pages, charts, images and other resources) is bound to the ASP.NET session life cycle. By default the ASP.NET session timeout is set to 30 minutes. Thus when ASP.NET session objects expire our cache management objects also expire. However if the memory usage is a concern you can configure our cache management as illustrated in the Configuring Cache help article or decrease the ASP.NET session timeout.
New HTML5/JS REPORT VIEWER with MOBILE AND TOUCH SUPPORT available in Telerik Reporting Q3 2013! Get the new Reporting version from your account or download a trial.