Noticed that every time I view a report using the module additional RAM is consumed and closing the report does not return the memory to the system.
It is therefore possible to consume all system memory simply by viewing the report multiple times.
Is there something I should be doing to make certain reports no longer being viewed are no longer using RAM?
This had been becoming a big problem as DNN would complain of out of memory errors throughout the day from frequent viewing of the reports.
I may have mitigated the symptom somewhat by creating a separate application pool for this portal and setting aggressive thread idle timeouts and recycle worker processes interval.
I think this may only help somewhat.
Is there something I'm doing wrong?
Excuse my rudeness, but I must say I'm disappointed that I've gotten no response to this.
I cotinue to have issues where viewing reports with this module causes runaway memory resource use and the viewer then crashes and presents users with ugly errors.
I must then reset IIS to get the viewer back online and return the memory to the system. I feel as if the viewer module may not be closing the report gracefully when the window is closed on the client side. But I am not the developer... that's Aricie.
So, is there something I can do to help you understand my issue? Data I have not provided, perhaps?
Is this something caused by a mistake I am making in implementation? Do you have any recommendations for configuration?
Sorry for not getting back to you on this. The person responsible for this module is out of the office and the problem has been looked after but not resolved so far. Be assured we take it into account and try to answer as quicly as we can. Thnaks for your patience, we'll get back to you shortly.
Thomas for Aricie Team
 Hi,
I've send you an email including PA CrystalReportViewer 2.1.1 (Beta).
This version should resolve memory use issue.