Skip Headers
Previous
Previous
 
Next
Next

Instance Investigation

In Instance investigation you drill down to the instance level of the type that holds on to the leaking objects. Here you look for an instance with an abnormal memory size or an abnormal amount of references being held and then inspect that instance. When inspecting an instance, you can see field names, field types, and field values. These values will hopefully lead you to the correct place for the error in the application code; i.e. where that particular instance of that particular type is allocated, modified, or removed, depending upon what the situation implies. Minimizing the problem areas to the ones connected to the suspected instance will most likely lead you on the right track to finding and fixing the actual problem that causes the memory leak.