This question is locked. New answers and comments are not allowed.
Hello,
I'll try to explain the annoying error that we are facing in one of our SL applications. We have drilled down to the RadGridView as the source of the problem, or at least it is related with it.
Our app uses RadDocking to presents several tabs to the user. One of the tabs is a realtime view which viewmodel requests data to a WCF Service every 10 seconds (it launches 4 calls to WCF each time, and all of them use anonymous delegates). The service response that affects the RadGridView is processed as follows:
The "ToObservableCollection()" function takes a List<T> as parameter and returns an observable collection of <T>. CT1Values is a property that implements INotifyPropertyChanged. The RadgridView is directly connected to it via ItemsSource = {Binding CT1Values, Mode=OneWay}
We know that re-creating the ObservableCollection bound to the RadGridView every time we get a response from WCF service is not optimal; however we consider it does not justify the following behaviour:
And then, IE, Chrome or Firefox start consuming 20-30% of CPU, the entire application becomes unresponsive for 5 minutes and finally, if you're lucky, comes back to life (not in Firefox, that finally kills the plugin-container.exe).
We have been able to reproduce this without the need of letting it running all the time. We just decreased the WCF request period (and therefore, the CT1Values update) to 200 milliseconds. Then, this happens in just 2 minutes.
We think this is related to the RadGridView because we tested the View placing only one UI Element at a time and re-running the test. All UI Controls (some of them our own usercontrols) worked perfectly... until we placed only the RadGridView, and then the 1 to 5 points story happened. We also tested replacing the RadGridView with the .NET GridView control, and it worked perfectly.
I hope you can provide any help. This app is intented to be always up and running, and typically showing the real time view in a big monitor without user interaction.
By the way, RadControls version is 2013.1.403.1050.
Thanks.
I'll try to explain the annoying error that we are facing in one of our SL applications. We have drilled down to the RadGridView as the source of the problem, or at least it is related with it.
Our app uses RadDocking to presents several tabs to the user. One of the tabs is a realtime view which viewmodel requests data to a WCF Service every 10 seconds (it launches 4 calls to WCF each time, and all of them use anonymous delegates). The service response that affects the RadGridView is processed as follows:
this.CT1Values = (from ......).ToObservableCollection().
The "ToObservableCollection()" function takes a List<T> as parameter and returns an observable collection of <T>. CT1Values is a property that implements INotifyPropertyChanged. The RadgridView is directly connected to it via ItemsSource = {Binding CT1Values, Mode=OneWay}
We know that re-creating the ObservableCollection bound to the RadGridView every time we get a response from WCF service is not optimal; however we consider it does not justify the following behaviour:
- Open the realtime view in a tab.
- Open other views in other tabs (remember we use radDocking). Those are not realtime views.
- Bring to front the realtime view tab and go home.
- Come back next day. The view is updating values (grid included), and everything works great apparently.
- Then, switch to another tab and switch back to the tab containing the realtime view.
And then, IE, Chrome or Firefox start consuming 20-30% of CPU, the entire application becomes unresponsive for 5 minutes and finally, if you're lucky, comes back to life (not in Firefox, that finally kills the plugin-container.exe).
We have been able to reproduce this without the need of letting it running all the time. We just decreased the WCF request period (and therefore, the CT1Values update) to 200 milliseconds. Then, this happens in just 2 minutes.
We think this is related to the RadGridView because we tested the View placing only one UI Element at a time and re-running the test. All UI Controls (some of them our own usercontrols) worked perfectly... until we placed only the RadGridView, and then the 1 to 5 points story happened. We also tested replacing the RadGridView with the .NET GridView control, and it worked perfectly.
I hope you can provide any help. This app is intented to be always up and running, and typically showing the real time view in a big monitor without user interaction.
By the way, RadControls version is 2013.1.403.1050.
Thanks.