Parent Binary

The Parent Binary view is effectively the same as the Object Type view, except that instead of displaying each object’s type, it displays the name of the object file that defined that type’s vtable.

What this view does not do is record the logical allocation point of an object, since that is simply not recoverable from the information available. For example, if some of your own code contains a CFoo::NewL() where CFoo is imported from a dll, then it will be an object file in the dll that is displayed for the resulting allocated cell, not the object file containing the call to NewL.

This view can be useful to quickly find a module that is contributing into a heap objects that are unexpectedly large, or that you do not expect to be there.

Related references