Improve the memory and the performance of RadPdfViewer when rendering big images
Loading a document that contains big images could lead to OutOfMemory exception.
Posted on:02 Oct 2014 10:07
As discussed with Kammen, it certainly would be a plus if the internal 32bit ARGB bitmap used in RadPdfViewer would not be passed to the viewer directly. If e.g. monochrome or grayscale images are converted, it would be nice to preserve the format and pass this to the viewer for rendering, since it would automatically save a lot of memory and some unnecessary "upscaling".
Posted on:24 Feb 2016 15:13
We have improved memory usage when rendering big images. The improvement is included in our latest 2016 Q1 SP1 release.
Do not hesitate to contact us if any issues or questions arise.
The Telerik Team
Posted on:13 Sep 2017 13:26
Is this really fixed? I have a 3,5 MB file within 20 pages of images (scans). The try to print this via RadPDFViewer kill the app with an out of memory (>1,4 gb)
Posted on:04 Apr 2018 12:50
In R1 2018 we have additionally implemented several improvements when rendering different type of images which are described in the release notes for PDF Viewer here:
If you still experience any issues you may open a support ticket and send us the problematic PDF files. This way we will be able to investigate the concrete case and decide whether to open a new feedback item.