In my application I am getting a lot of undisposed instance like System.Linq.Enumerable.WhereListIterator<TestbenchChannelObj> and I have no idea where is it coming from.
I found in the forum the following older topic about a similary problem:
http://memprofiler.com/forum/viewtopic. ... light=linq
Is the behavior I see still a bug?
The bug in the post you are referring only occurred for value types and only in .NET Memory Profiler 2.6. This bug is fixed in v3.x and
System.Linq.Enumerable.WhereListIterator<TestbenchChannelObj> is a class, so this should not be causing your undisposed instances.
I'm not aware of a bug or other issue that should cause the profiler to falsely classify instances as undisposed. What version of the profiler are you running?
Have you investigated the allocation call stacks of the undisposed instances? They should reveal who creates the instances, and hopefully also why they are undisposed. If you include a call stack for an undisposed instance in your reply, I will get some additional information and then I can hopefully give you a better explanation.
SciTech Software AB
Thank you for your answer but because I have time pressure in my project now, I decide to remove the LINQ request from my code and replace them by "standard code".
I still don't know where the problem is coming from but now I have no more memory leaks (at least because of LINQ).
Users browsing this forum: No registered users and 29 guests