Hello,
I've been profiling an application which makes extensive use of the XamDataGrid. Next to DataBinding, the #2 most memory hungry element in the application is CellValuePresenter object. It is not releasing allocated memory and continues to grow with use. There is also a huge litter of WeakReferences created by it's use. Also bad because they should be getting collected.
Our business requirement insists this application be running and in use 24 hours /day. In it's current state, it normally last 3-4 hours without restarting - very undesirable for a highly available application.
Is Infragistics and others aware of this? Is there a fix or at least a way to minimuze or de-allocate the consumption?
Have others tried alternative products that do a better job of garbage collection?
Thanks,
Glenn
Hello Glen,
I have been looking into your issue and was hoping you could provide us with a more detailed description of your project so I can do more detailed research on your specific scenario.
Thanks in advance. Looking forward to hearing from you.
No response from you on the previous? Do you want me to send you anything specific? Project is VS 2008. I am using roughly 7 XamDataGrids in 1 application. As indicated the CellValuePresenter is the biggest memory hog on the system. Taking more than Outlook or any other application running.
The second hungriest object is the DataBinding object. I expect Infragistics is leveraging the WPF DataBinding library and therefore controls the number of objects in this group.
Both are having a huge impact on the application.
I’ve read the technical document on limiting attributes, formatting, the use of Auto on column etc. All negligible in this case.
If the themes and formatting impact your application to that degree, then it’s not really worth using.
Time to look for another product?