New to Telerik Reporting? Download free 30-day trial
The WPF Report Viewer can be hosted in different types of controls, producing a number of scenarios where the resources, occupied by the viewer, cannot be disposed automatically, thus causing a memory leak. The default behavior of WPF Report Viewer is to create its model when instantiated and dispose it when its owner window is closed. The Report Viewer instance adds a handler to the owner window's Closed event to ensure that the model and its resources will be disposed when the window is closed. This corresponds with the most common case of hosting the WPF Report Viewer in a WPF Window. However, in some scenarios an additional action must be taken to ensure the correct workflow and resources disposal. Below are shown some specific cases of embedding the WPF Report Viewer in another control.
When the RadWindow is closed, the report viewer disposes its resources. The RadWindow is optimized to be shown again without being instantiated, which would put the Report Viewer in an invalid state, because the report viewer model is already disposed, but not yet created. In this scenario it is necessary to set the property AutoDisposeModel to false to prevent disposing it when the RadWindow is closed. The model can be explicitly disposed when necessary with calling the DisposeModel method.
In this scenario the WPF Report Viewer is hosted in a RadTabItem that is being activated and deactivated while the user navigates through the tabs in the RadTabControl . The report viewer and its model are not disposed when the tab loses focus in order to persist the viewer state and avoid reloading it when the tab receives focus again. In this scenario the report viewer is kept in memory until the owner window is closed. The default behavior of the WPF report viewer will ensure that the resources are properly released.
In this scenario the WPF Report Viewer is hosted in a RadTabItem that is being removed from its RadTabControl host. Since the owner window is not closed, the disposal routine is not called and the report viewer doesn't release the occupied memory, because it holds a reference to its owner window. In this scenario it is necessary to call the method DisposeViewerResources and make sure the property AutoDisposeModel is set to its default value true. The disposal method can be called on Unloaded event of either the viewer or the RadTabItem host.
The scenarios above are a few of the available variations of embedding the WPF Report Viewer in another control. It is always advised to examine the memory consumption of the application and use the explicit methods of disposing the viewer resources if necessary.