Hi,
We've just started to look at the ScheduleView control within our silverlight application, and I've noticed that any UserControl with a ScheduleView on it doesn't get garbage collected when we remove it from the visual tree.
Our application uses MEF to create instances of required UserControls, when chosen from a menu, which are then displayed as the content of a ContentControl in the main work-area of our application. When the selected menu item changes the UserControl is removed from the visual tree, and replaced with the new UserControl and normally the removed UserControl then gets garbage collected (we have a weak reference within the app that allows us to check whether this has happened or not). However, if I add in a ScheduleView onto such a page, with nothing defined within the ScheduleView at all, then the garbage collection stops happening. I have played about creating the schedule view dynamically in code behind and adding it to my grid that way, and removing it as part of my UserControls cleanup code, but it has made no difference.
We have performed no styling of the control and have no memory issues with any of the other Telerik controls.
I have seen a few other postings relating to memory leaks, but they referred to specific aspects of the control. Can you confirm whether or not the entire control is currently impossible to display and then dispose of such that it can be garbage collected? Given that our application relies on creating and destroying UserControls as and when required, such behaviour would be a major issue for us.
We are on Q3 2012 SP1 of the Telerik tools.
Thanks,
Colin.
We've just started to look at the ScheduleView control within our silverlight application, and I've noticed that any UserControl with a ScheduleView on it doesn't get garbage collected when we remove it from the visual tree.
Our application uses MEF to create instances of required UserControls, when chosen from a menu, which are then displayed as the content of a ContentControl in the main work-area of our application. When the selected menu item changes the UserControl is removed from the visual tree, and replaced with the new UserControl and normally the removed UserControl then gets garbage collected (we have a weak reference within the app that allows us to check whether this has happened or not). However, if I add in a ScheduleView onto such a page, with nothing defined within the ScheduleView at all, then the garbage collection stops happening. I have played about creating the schedule view dynamically in code behind and adding it to my grid that way, and removing it as part of my UserControls cleanup code, but it has made no difference.
We have performed no styling of the control and have no memory issues with any of the other Telerik controls.
I have seen a few other postings relating to memory leaks, but they referred to specific aspects of the control. Can you confirm whether or not the entire control is currently impossible to display and then dispose of such that it can be garbage collected? Given that our application relies on creating and destroying UserControls as and when required, such behaviour would be a major issue for us.
We are on Q3 2012 SP1 of the Telerik tools.
Thanks,
Colin.