Any Infragestic control you use leaks memory. In testing, I've found that UltraTextEditor, UltraTabControl, UltraComboEditor, UltraButton, etc... All do not dispose of themselves correct and all are held in memory due to a strong reference from Infragestics.Win.Office2007ColorSchemeChangedNotifier, which is held by a static event handler.
Just recently the major memory leaks with win tree were reduced to a point where it could be used in production code. I did a sweep of a couple sub system to use all Infragestic control to take advantage of themeing and when from 20-30k memory leaked per sub system instantiation to 5 megs+ leaked.
Seeing how bad the leaks are, surely someone has a work around? Is there a hot fix for this yet?
Thanks for confirming the case number.
In reviewing the case, I see that we found a couple of things.
First, there is some increased memory usage whenever a new Appearance object is created, as the Appearance objects hook into our Application Styling Framework. This is expected behavior, because the controls need to be ready to react appropriately if Application Styling is turned on by the application at a later point during execution.
Second, we'd asked for some specific diagnostic information, which we need to continue our research. There may be other things causing an apparent memory leak besides the ones related to application styling. We never received the requested information, and so we cannot confirm whether there is or is not a memory leak.
If you can provide the requested diagnostic information, you can reopen the support case within 30 days of its closure, and we will continue research. After 30 days of the case's closure, you can instead submit a new support request and refer to the original one.
CAS-17445-P1U2TR
tribbles,
What is the case number from your support request? I'd like to follow up on this issue to make sure that we've covered all of the avenues that we reasonably can cover.
I open a support ticket, the result was that this was expected behavior. :( However, with my pop-up editor usage I'm leaking a couple thousand objects an hour and I run out of reosurce handles and the software crashes. The recommendation from teh support ticket was not to recreate those editors so often. :( I did have a sample program with the support ticket to show case, but with a simple window you are only leaking a couple objects and at most 10k a go, which they deemed harmless.
I am seeing this as well. I have verified that the Infragistic's control is Disposed of and fires its' Disposed event but this static is keeping the control around. I haven't had time to recreate this in a sample app but here is what our memory profile shows after the UltraListView has been Disposed of.