Object is disposable but Dispose() has not been called yet.
phaeze
Posts: 7
Hi,
I am in the midst of debugging a memory leak in a WPF app, I have found the object that is being held in memory but am having a hard time understanding the graph to find the cause.
Looking at the instance retention graph there are several objects that have the green coloring, which on mouse over says "Object is disposable but Dispose() has not been called yet." This is strange as I have debugged through the code and I know dispose is being called on these objects.
Is there some explanation as to why ANTS would believe otherwise?
Thanks,
Phaeze
I am in the midst of debugging a memory leak in a WPF app, I have found the object that is being held in memory but am having a hard time understanding the graph to find the cause.
Looking at the instance retention graph there are several objects that have the green coloring, which on mouse over says "Object is disposable but Dispose() has not been called yet." This is strange as I have debugged through the code and I know dispose is being called on these objects.
Is there some explanation as to why ANTS would believe otherwise?
Thanks,
Phaeze
Comments
Thanks for your post!
There aren't any issues with the disposed object tracking that I'm aware of--would you be able to share your application with us so we can reproduce this in-house?
Jessica Ramos | Product Support Engineer | Redgate Software
Have you visited our Help Center?
Thanks for your reply.
Regards,
Phaeze
Jessica Ramos | Product Support Engineer | Redgate Software
Have you visited our Help Center?