Need help with memory profiling and filtering

I don't mean to be a whiner, but I simply can't wrap my brain around memory profiling and filtering. When I take memory snapshots with filtering set to hide all namespaces except mine, the Namespace tree still shows System as holding 95.75% of the resources and my namespace as holding just 0.82%. Shouldn't all the memory usage be folded up into my namespace? If I have one custom object that holds 1,000 images, shouldn't all the memory usage belong to that one custom object? I'm truly baffled that I'm the only one who thinks this way.

1 comment
Comment actions Permalink

Here is another example. When I get a memory snap shot, System.String is almost always the largest consumer of memory. Isn't it more important for me to know who is holding the most strings? Especially if I have the filters set to show only my namespace, wouldn't it make sense that I'm more interested in seeing which object I'm using that contains the most strings? When looking at a hierarchical view of a Windows application, shouldn't the biggest user of memory be the application's main window?


Please sign in to leave a comment.