Completed
Last Updated: 12 Mar 2019 08:39 by ADMIN
Loading a document that contains big images could lead to OutOfMemory exception.
Completed
Last Updated: 13 Feb 2023 15:52 by ADMIN
Release LIB 2023.1.220 (20 Feb 2023)
Scanned image is not visible with the new engine  
Completed
Last Updated: 20 Apr 2016 08:56 by Ludwig
We have a good news for all of you who have experienced problems with the memory consumption of RadPdfViewer. We have made significant optimization of what is cached for each page when scrolling in a document.
Please have in mind that when using big images in a document the optimization may seem not so significant. This is because there is additional opportunity to further optimization of the caching mechanism for the image sources.
I have logged this additional opportunity as a different feature request. Here is a link if you would like to subscribe for status updates of that item to: Optimize the image source cache - http://feedback.telerik.com/Project/143/Feedback/Details/189305-optimize-the-image-source-cache
Completed
Last Updated: 17 Dec 2015 12:13 by Christian
ADMIN
Created by: Deyan
Comments: 1
Category: PDFViewer
Type: Bug Report
7
The fix will be available in our official release Q1 2016.
Completed
Last Updated: 26 Jun 2023 13:51 by ADMIN
Release R2 2023 SP1
When a PDF document contains images compressed with CCITTFaxDecode with applied BlackIs1 parameter, black color is visualized as white and white as black.
Completed
Last Updated: 02 Feb 2016 07:35 by ADMIN
ADMIN
Created by: Nikolay Demirev
Comments: 12
Category: PDFViewer
Type: Bug Report
6
Printing document on a machine with .NET Framework 4.6 installed does not work for some documents.

Currently, an issue is opened at Microsoft Connect: "Printing with PrintDialog fails when .NET 4.6 is installed" (https://connect.microsoft.com/VisualStudio/feedback/details/1980419/printing-with-printdialog-fails-when-net-4-6-is-installed).

Workaround: In the attached project.
Completed
Last Updated: 16 Sep 2020 12:34 by ADMIN
Release R3 2020
This is caused by an incorrect order of applying the TextMatrix and the glyph stroking operation.
Unplanned
Last Updated: 10 Apr 2020 14:08 by ADMIN
Visualizing a page with a huge number of images (40000) freezes the application.
When switching to the FixedDocumentSinglePageViewPresenter, all the page content should be loaded so it can be later rendered. Although the images are loaded asynchronously, there are too many threads started which seems to cause the hang. Also, according to profiling results, it seems like the image caching causes performance diminishments in such scenarios. 
Completed
Last Updated: 15 May 2023 09:27 by ADMIN
Release R1 2018
Due to excessive memory consumption when decoding images, OutOfMemoryException can be thrown when viewing documents with large images inside them. 

Workarounds: 
- Set ExtensibilityManager.MaxImageSize = null. This will skip one resizing step, and could be beneficial in documents containing few large images.
- Use 64-bit process for the client application. This allows the process to consume much more memory. Note that starting 64-bit process while debugging can be tricky, as described in this blog post: https://weblog.west-wind.com/posts/2016/Dec/19/Visual-Studio-Debugging-and-64-Bit-NET-Applications.

Available in R1 2018 Official release version.
Unplanned
Last Updated: 13 Oct 2017 14:09 by ADMIN
The images are loaded asynchronously and when scrolling too fast, the loader might fail to load an image if it is bigger.
Completed
Last Updated: 27 Mar 2023 11:41 by ADMIN
Release LIB 2023.1.327 (27 Mar 2023)
Created by: Frank
Comments: 2
Category: PDFViewer
Type: Bug Report
5
No images are shown when opening a file.
Unplanned
Last Updated: 10 Aug 2020 12:34 by ADMIN
RadPdfViewer does not read image resources defined in Form XObject elements.
Unplanned
Last Updated: 23 Jun 2022 08:13 by ADMIN
Handle the cases when the page is rendered slowly and the document appears empty
Completed
Last Updated: 17 May 2023 06:31 by ADMIN
Release R2 2023
Completed
Last Updated: 19 Jan 2023 14:56 by ADMIN
Release R1 2023
When specific culture is set (e.g. Hebrew but not only) in a project targeting .NET 5 (or later), some documents are not rendered correctly (rendered as blank pages).
Completed
Last Updated: 06 Mar 2019 06:46 by ADMIN
This exception is thrown because there is field name with special characters which are incorrectly modified during the recalculation process of widget appearances. This exception is thrown in the internal RecalculateMissingAppearances method or in RecalculateWidgetAppearancesOld method.
Completed
Last Updated: 18 May 2023 06:50 by ADMIN
Release R2 2023
This is reproducible for images with FlateDecode and predictor value in the range between 10 and 15. As an example you may take a look at the DecodeParms property in the following image PDF dictionary:

<< /BitsPerComponent 8 /ColorSpace /DeviceRGB /DecodeParms << /BitsPerComponent 8 /Colors 3 /Columns 1024 /Predictor 15 >> /Filter /FlateDecode /Height 2868 /Subtype /Image /Type /XObject /Width 1024 /Length 1236707 >>
Completed
Last Updated: 14 Feb 2023 06:36 by ADMIN
Release LIB 2023.1.220 (20 Feb 2023)
The issue is reproducible only for some specific font files. The characters are displayed as rectangles. This seems to caused by incorrect glyph name and glyph id mapping.
Completed
Last Updated: 13 Feb 2023 15:55 by ADMIN
Release LIB 2023.1.220 (20 Feb 2023)
Some Image XObjects are imported but not displayed in PdfViewer.

It seems all the documents contain scanned images produced by a Lexmark scanner.
Completed
Last Updated: 27 May 2021 10:11 by ADMIN
Release LIB 2021.2.531 (31/05/2021)
When there is no ToUnicode CMap, the text from the Simple Font instance should be extracted by mapping the glyph name to its corresponding charcode according to Adobe Glyph List. Additionally, the Differences array should be included in these calculations when there is custom encoding. The current implementation of RadPdfViewer makes ToString to the original char id byte value which leads to wrong characters. 
1 2 3 4 5 6