The fix will be available in next LIB release (v. 2015.1.0323).

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

The fix will be available in our official release Q2 2016.

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.

The fix will be available in our official release Q1 2016.

I have a pdfviewer bound to a richtextbox like in your samples. But I want to keep the wpf viewer in fit to window scaling mode while changing the content of the richtextbox.

Right now the pdfviewer will rescale to 100 % on each update.

The issue is closed as duplicated to the following item: http://feedback.telerik.com/Project/143/Feedback/Details/141105-tiling-patterns-are-rendered-wrong-when-some-transformation-is-applied

The fix will be available in our official release Q2 2015 SP.

The fix will be available in our next LIB release (v. 2015.02.0706).

The fix will be available in our next LIB release (v. 2015.02.0706).

The fix will be available in our official release 2015 Q2. 

The feature  will be available in our official release 2015 Q2. 

The fix will be available in our latest LIB release (v. 2015.1.0323).

The fix will be available in Q3 SP.

The feature was implemented for Q2 2014.