I've noticed that I have this huge memory leak.My app relies heavily on infragistics ui components, and our code createsAnd destroys many UserControls that comprise mostly of UltraTextEditors.After some research I found that the constructor is not called on ANY control that contains an UltraTextEditor (and probably other editors as well).
This seemed so weird to me that I started a new project, that contains a main form, and a single user control, which in turn contains a single UltraTextEditor. I added a destructor to this control, and set it to print a message to the debug console.To the main control I added a single button that creates my user control and looses reference to it, and then a call to GC.Collect();.
If the control contains the UltraTextEditor, the descructor is never called, if I remove the line with "this.controls.add(ultraTextEditor1); " the destructor is called as expected.Why does this happen? Is there some setting I need to know of somewhere that prevents my control from being GCed? Does the UltraTextEditor save a reference to the parent class in some static place that never gets out of scope?
Thanks yossin. I will take a look and let you know how it goes.
pathennessy said:I agree. This is very disappointing and a serious design flaw. I won't be able to recommend their product suite to clients until this is resolved.
Have you contacted developer support regarding this issue? If you can duplicae the problem, you should Submit an incident to Infragistics Developer Support so they can get it corrected.
you can find a fix for this problem at my blog here
(http://subjectively.blogspot.com/2009/03/importance-of-recycling-memory.html)
i dont know if it will work for other releases, but you can try.
I agree. This is very disappointing and a serious design flaw. I won't be able to recommend their product suite to clients until this is resolved.
I'd like to see how you resolved this issue and will look for your blog. Thanks.
hi,
it seems infragistics are unwilling to resolve this issue.
i've contacted them back in june of last year, several versions since the issue has not yet been resolved.
i created a fix for this issue that works on v.73 i dont know if it will work on later versions, but i suspect it might.
what we did was to directly access and release the objects that hold references to all our UI objects.
this code will be available soon on my blog.
if you want to get it sooner, contact me and i will send you a copy of the source code.
i have to say, i am very dissapointed with infragistics for not fixing this core issue.
this is not a "minor issue". this is a fundamental design flaw.
sending a product that cannot be garbage collected and results in huge memory leaks, and not resolving it version after version showes complete disragard for me as a client.