Object is disposable but Dispose() has not been called yet.

Memory profiling for .NET developers

Moderator: dom.smith

Object is disposable but Dispose() has not been called yet.

Postby phaeze » Fri Jun 13, 2014 6:52 pm

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
phaeze
 
Posts: 2
Joined: Fri Jun 13, 2014 6:46 pm

Postby jessica.ramos » Mon Jun 16, 2014 7:15 pm

Hi there,

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
Technical Support
Red Gate Software Ltd.
jessica.ramos
 
Posts: 235
Joined: Mon Apr 23, 2012 1:13 pm

Postby phaeze » Mon Jun 16, 2014 8:04 pm

Unfortunately I cannot share the application as it is proprietary, and at this point we have found a simpler display of the issue via visual studio's minidump debugging. Though we have not yet found the issue.

Thanks for your reply.

Regards,
Phaeze
phaeze
 
Posts: 2
Joined: Fri Jun 13, 2014 6:46 pm

Postby jessica.ramos » Mon Jun 16, 2014 9:04 pm

Ah okay, I understand if the application can't be shared. Just to confirm--is Visual Studio also reporting the objects as not disposed then?
Jessica Ramos
Technical Support
Red Gate Software Ltd.
jessica.ramos
 
Posts: 235
Joined: Mon Apr 23, 2012 1:13 pm


Return to ANTS Memory Profiler 8

Who is online

Users browsing this forum: No registered users and 1 guest