- System requirements
- Profiler architecture
- Profiler installation
- Uninstall profiler
- Running the profiler
- Profiler activation
- Welcome screen
- Start profiling
- Profiling overhead
- Snapshots
- Solving performance problems
- CPU profiling
- Thread profiling
- Object allocation profiling
- Memory profiling
- Exception profiling
- Telemetry
- Probes: monitor higher level events
- Inspections: automatic recognition of typical problems
- Automatically trigger actions on event
- Automatic deobfuscation
- Summary, automatic deobfuscation
- Filters
- Profiler command line
- Command line tool to control profiling
- Export of profiling results to external formats
- Profiler .NET API
- Profiler HTTP API
- Settings
- Troubleshooting
Group objects by category
Analyzing .NET memory snapshots can be a daunting task due to the vast amount of objects and data involved. Grouping objects by various categories can make it easier to identify memory issues like leaks or high utilization. Here is how you can categorize objects in a .NET memory snapshot:
Group by class
Grouping objects by their classes allows you to see which classes occupy the most memory.
Group by class and namespace
Grouping objects by their classes and namespaces provides a logical structure that's easy to navigate.
Group by domain and module
By grouping objects according to their domain and module, you can quickly identify which area of the application is contributing to memory issues, allowing you to address the root cause more effectively.
Group by generation
Grouping objects by their generation can indicate how long objects are lingering in memory.
Group by shallow size
Shallow size is the amount of memory directly allocated for each object. Grouping by shallow size helps you find objects that are individually large.