The memory consumption is increasing each time the Document property is changed at runtime. This memory doesn't get collected by the GC. To reproduce this, the Document property changes should happen with a small time interval between them. For example, several consecutive button clicks. Also, in order for that to be presented, the RadPdfViewerNavigationPane should be used and bound to the RadPdfViewer.

The issue is not reproducible if there is enough time between the Document changes, so that the UI is properly loaded.

To avoid the memory leak, avoid using the RadPdfViewerNavigationPane.