Objects set view restriction on number of objects

I go to view the Object set of a snapshot then I click on the instances view. However, I can see the list only displays the first 500 objects and it seems these are sorted by the retained bytes.
The question is which 500 items are being displayed and what sort was applied to come up with this list.
Then, is there any way of viewing the remaining objects as these might be the objects of concern?

Comment actions Permalink

Hi Allan

It's the first 500 objects sorted by column and direction of your choice. Use sorting by column and filtering by type name to find an interesting object.
Could you please explain more detailed your use case when you need to investigate manually more then 500 objects?

Please tell us if sorting and filtering possibilities is not enough to find data you need to solve your memory issue.

Comment actions Permalink

Thanks, that answers my question. So based on your explanation, I can sort by the retained bytes and know that I am looking at the most memory intensive instance and tackle that to get the best saving in memory.

In terms of the filtering, the problem is I am looking at 48K objects of the same .NET type. So the filtering doesn't help me in terms of restricting based ont attributes on the objects.

Comment actions Permalink


If you analyze object set with  48K objects of the same type, instances view is not useful in this case. Please use group by similar retention view. If all of 48K objects retained by the same way, you can open any instance. In other case you should analyze retention paths to narrow down searching scope.

Comment actions Permalink

The dotMemory paradigm is reducing amount of suspected objects. All our views allow slice and dice whole objects graph to do that.
First of all you can use Sunburst Chart view to find a groups of object or even subsystems retains the most memory amount and select only them for further investigation.
If you need to investigate objects which are not retained exclusively (not dominated) you can use Group by similar retention view to slice them onto groups by most different paths of retention.
Group them by type and select only important for you etc.
After all you will have a set of identical objects then you can open any of them (because they are identical) and investigate why it is not collected using Key retention path view or other.

Hope it helps


Please sign in to leave a comment.