This is a migrated thread and some comments may be shown as answers.

Adding Control.DataVisualization to App.xaml uses enormous amounts of RAM on View creation

2 Answers 64 Views

GridView

This is a migrated thread and some comments may be shown as answers.

Andy asked on 05 Dec 2019, 04:00 PM

tuggersview-xaml.jpeg

I have a problem trying to use another Telerik component (-> RadTimeBar) which leads to a not loading application with a lot of memory consumption. I am using NoXaml assemblies so I figured I have to add DataVisualization to the App.xaml ResourceDictionary in order to see the control (because it is "invisible" so far). As soon as I add Control.DataVisualization to the App.xaml ResourceDictionary the application is no longer starting properly. It tries to initialize the first visible "start page" called TuggersView.xaml which uses a Telerik RadGridView. However the View initialization call never returns and meanwhile the application uses above 4GB of RAM before I kill the process. Running in debug the application usually consumes around 400 to 500 MB when loaded completely.

Have you ever encountered this kind of behaviour?

App.xaml Ok:

App.xaml issue:

Product Bundles

DevCraft

Web

Mobile

Document Management

Desktop

Reporting & Mocking

Automated Testing

CMS

UI/UX Tools

Debugging

Free Tools

Support and Learning

Productivity and Design Tools

Adding Control.DataVisualization to App.xaml uses enormous amounts of RAM on View creation

2 Answers, 1 is accepted