Hi, we encountered some problems with some of our customers using the viewer version 2.16 and asp.net.
We use HtmlBasedEngine property set to "true" and the property PreloadPagesCount set to "2".
We noticed that especially with files that contain a relatively large number of pages (greater than 10), the iis pool begins to consume a lot of RAM, as well as the private memory used.
This is because even if it is set to 2 the number of pre-loaded pages, the viewer continues to write the pages rendered in html on the cache folder, until that have not been rendered all the pages.
If you multiply this problem for a large number of users, the issue it raises is an exception of SystemOutOfMemory and consequently the recycle of the pool, and then the expiry of asp.net sessions.
Now we have turned off the viewer on the customers who experienced this problem, but we have to give a solution to these customers.
The thing that we do not understand is the use of the property PreloadPagesCount which in this case is ignored.
We are waiting for your feedback.