Memory Leak problems

Reply

walterG Posted: 11-07-2008 6:35 PM

 Hello !

I believe that almost all infragistics controls have memory leak issue. I have discovered it because my application is using to much memory so i have invastigated first on my application and next by making some simple examples(using only one or two control) and using a memory profiler.

Now, the problem is that every infragistics control is referenced by a delegate called "themeChangedDelegate" and as a conseguence the GC cant return that memory to the OS. if you are not aware of this problem and cannot replicate this issue, i can make a video with a very simple example.

Hope to see fixed this issue as soon as possible.

Thank you.

Best Regards.

ps: i'm using 2008 vol2.

Reply

Christopher Bishop replied on 11-07-2008 11:07 PM

rated by 0 users

I noticed a similar problem with the winGrid 8.2 in my example email application but the memory problem went away in 8.3 not sure about the other controls but the memory problem i was facing has disapeared... I just tried to replicate the memory leak that you are refering to as mine was something different but could not find a leak in the themeChangedDelegate delegate so I for one would be interested in a video example so I could test it on my machine to...

Reply

walterG replied on 11-08-2008 3:41 AM

rated by 0 users

Hi Bishop,

here are the videos.

http://www.focuslab.eu/public/infragisticsmemoryleak/t1/t1.html

http://www.focuslab.eu/public/infragisticsmemoryleak/t2/t2.html

Reply

Christopher Bishop replied on 11-08-2008 11:29 AM

rated by 0 users

Couple of things, first the reason you see Form in "Shortest root path" is because it is part of .Forms... Custom dll files, controls etc. are not part of those objects...

Setting a object to Null does not mean that the GC is going to collect it, furthermore the GC.Collect method is not guaranteed to Collect nor destroy objects in memory as it has a mind of its own, however setting a objects IDisposable and/or Object.Dispose does allow the gc to clean up a little better than Null.

 I am pretty swamped this weekend but will try to get to making a video to show what I mean and does not produce the same results as your videos.

Reply

walterG replied on 11-09-2008 4:25 AM

rated by 0 users

Chris Bishop:

Couple of things, first the reason you see Form in "Shortest root path" is because it is part of .Forms... Custom dll files, controls etc. are not part of those objects...

Setting a object to Null does not mean that the GC is going to collect it, furthermore the GC.Collect method is not guaranteed to Collect nor destroy objects in memory as it has a mind of its own, however setting a objects IDisposable and/or Object.Dispose does allow the gc to clean up a little better than Null.

 I am pretty swamped this weekend but will try to get to making a video to show what I mean and does not produce the same results as your videos.

first,

if you have an instance of a class(aka object) referenced only once and than set to null that reference, that instance is going to be destroyed as first as the GC see that it is no longer referenced.

second,

calling Dispose method it does not mean that the GC "Clean up" better the memory! The purpose of IDispose is that the class which implements it

is using unmanaged resourses so the programmer of the class must take care of this because the GC cant do this job!

Reply

Christopher Bishop replied on 11-09-2008 9:50 AM

rated by 0 users

It would seem that your knowledge of what dispose actually does is amazingly superior to mine so forgive my attempt at trying to help you understand, you have my deepest apologizes for my total Noob answer.

Thanks for the most excelent information about how Null/Nothing works "in C# / VB.NET" I guess I am just confused with how VB6 handles objects.

Reply

rkoops replied on 12-10-2008 9:20 AM

rated by 0 users

I am experiencing serious memory leaks. Among other controls I do use Infragistic controls. I have for example a dialog containing an infragistics webtabcontrol. If I click on all 7 tabs I have lost 3MB on the server.

Have you received a solution from Infragistics or did you find a workaround for the themeChangedDelegate.

Roland

Reply

walterG replied on 12-10-2008 10:02 AM

rated by 0 users

as you can see no answer.

Reply

Matt Snyder replied on 12-10-2008 10:12 AM

rated by 0 users

If you require the developers to look into the issue or require a formal response, you should submit this issue through Developer Support.

-Matt

Reply

yossin replied on 03-19-2009 1:10 PM

rated by 0 users

hi everyone, we encountered this issue a while back in vol 7.3 we have a workaround for this issue.

i dont know if it will work with current versions, but you can try.

the solution and explanation of the problem (basically infragistics is rooting all controls to static event handlers) can be found here

(http://subjectively.blogspot.com/2009/03/importance-of-recycling-memory.html)