I am observing the following: Given a simple WPF application that uses Crystal Reports WPF viewer (CR Runtime for Visual Studio SP20 installed): as soon as the report is loaded in the viewer, the application starts consuming CPU (2-5% on two-core machine), and that load persists for as long as the WPF form with WPF viewer remains on screen.
The load is not observed when the viewer is on screen without the report. Apparently, that load is caused by the viewer's load animation (gradient bagel which is shown by CR WPF report viewer while the report is being loaded), which continues counting and updating the rotation transformation even after the report is loaded and the animation is collapsed.
This is observed at least on Win 10 Anniversary Update with .NET 4.7 and on Windows 2012 R2 with .NET 4.6.1 Questions:
- Is it a known problem?
- If so -- are there ways we could apply in the application utilizing the CR WPF report viewer to avoid that CPU load?
- Crystal Reports for Visual Studio SP 20
- VS 2015
- Windows 10
Reproducing the Issue
The issue has been duplicated so it will be escalated to R&D for a solution and set for SP 22, due out in December or January 2018, not dates planed for SP 22 at this time.
cr for vs, WPF viewer, animation , KBA , BI-DEV-NET , BI Software Development Kits (SDKs) - .NET or Other , Problem