This question is locked. New answers and comments are not allowed.
Hello
I've been working on the developement of a Silverlight based ERP which uses numbers of telerik controls
One of my main component is a very complex control based on WCF which uses a combination of RadGrid, RadTabControl, RadContextMenu, RadSettings, RadWindows, customFilterDescriptors and Custom generated GridViewColumns
After a while, I got everything working as expected, without errors of any kind (as far as debug can tell), but the thing is, after using it for a while (depending actually on how many times we regenerate the itemsource), the grid, the tabcontrol and the context menus become unresponsive.
Basically, the application slows down until almost complete stop, and the user needs to recall the entire component to get the usercontrol responsive again.
The memory consumption doesn't seem to get out of hand, firefox shows a process using around 270Mo RAM, which doesn't strike me as exceptionnaly high, which begs the question is it really about memory leaks.
Does the telerik team has any idea or thought about the reason why this component would slow down like that ?
I've been working on the developement of a Silverlight based ERP which uses numbers of telerik controls
One of my main component is a very complex control based on WCF which uses a combination of RadGrid, RadTabControl, RadContextMenu, RadSettings, RadWindows, customFilterDescriptors and Custom generated GridViewColumns
After a while, I got everything working as expected, without errors of any kind (as far as debug can tell), but the thing is, after using it for a while (depending actually on how many times we regenerate the itemsource), the grid, the tabcontrol and the context menus become unresponsive.
Basically, the application slows down until almost complete stop, and the user needs to recall the entire component to get the usercontrol responsive again.
The memory consumption doesn't seem to get out of hand, firefox shows a process using around 270Mo RAM, which doesn't strike me as exceptionnaly high, which begs the question is it really about memory leaks.
Does the telerik team has any idea or thought about the reason why this component would slow down like that ?