I am investigating a customer issue where our WPF application crashes with an Out of Memory Exception when loading PDF Documents into the PDF Viewer, consuming around 1.4GB of RAM. Our application is a whiteboard style app where user can load multiple Viewers on to a large canvas space. This customer’s canvas has 37 PDFs on it, total file size is 70MB with most of the pdf content being images.

We have found that the application doesn’t crash on certain PCs. We think we have narrowed this down to Crashes on Win10 1903 and doesn’t crash on Win10 1809. The app is 32 bit, upgrading to 64 bit does seem to resolve the issue but that’s quite a significant change for us. We have upgraded the viewer to the latest version (V4.16.2704).
Questions:

Consuming so much memory from such a small total file size footprint seems strange.

I’m struggling to rationalize how the windows version is making a difference are others experiencing this.

Hi Paul,

Thanks for your reply, We are considering other options to how we architect the application, Unfortunately, unloaded the content based on viewport won't yield significant benefit as our viewport can be quite (very?) wide, upto 20 meters but typically around 5 meters. I think we might render the current page as an image and then load in the PDF when a user interacts with it.

I'm more trying to find out why this is breaking now, all things being equal only the windows update has changed and now the application crashes.


Could you expand on your comment of 20MB per viewer instance, how did you get to that number?

Ah no worries, I thought that might be a fixed overhead of the viewer. My experimentation is showing a 12MB PDF of 5 images is consuming around 50MB of memory.