What are the challenges you face when working across database platforms? Take the survey
Options

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

phaezephaeze Posts: 7
edited June 16, 2014 4:04PM in ANTS Memory Profiler 8
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

Comments

  • Options
    Jessica RJessica R Posts: 1,319 Rose Gold 4
    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 | Product Support Engineer | Redgate Software

    Have you visited our Help Center?


  • Options
    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
  • Options
    Jessica RJessica R Posts: 1,319 Rose Gold 4
    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 | Product Support Engineer | Redgate Software

    Have you visited our Help Center?


Sign In or Register to comment.