Understanding memory Profiler
jofreder
Posts: 4
I am test the trail version on a real problem to see how well it works to help justify the purchase.
OK, I look at the Live and total of memory and see that between snapshots these are staying the same on some classes.
Know is is safe to save because the two values are staying the same that this is a memory problem.
Now, how do I further investigate the problem. I know there is probably nothing that will just point right at it but the class view simply tell me the class name. Do I now look into objects? How do I go about looking at them to dig deeper into the problem.
Thanks
Joe
OK, I look at the Live and total of memory and see that between snapshots these are staying the same on some classes.
Know is is safe to save because the two values are staying the same that this is a memory problem.
Now, how do I further investigate the problem. I know there is probably nothing that will just point right at it but the class view simply tell me the class name. Do I now look into objects? How do I go about looking at them to dig deeper into the problem.
Thanks
Joe
Comments
The analysis can be done in many ways, but I think the next step for me would be to have a look in the all objects tab, filter the type of object with the most live instances, and sort it by age. The objects that are surviving the most garbage collections, I think, would be the 'problem children' to weed out first.