- System requirements
- Profiler architecture
- Running the profiler
- Profiler activation
- Start profiling
- Connect to profiled application
- Capturing snapshots
- Solving performance problems
- CPU profiling
- Memory profiling
- Garbage collection
- Exception profiling
- Probes: monitor higher level events
- Performance Charts
- Inspections: automatic recognition of typical problems
- Automatically trigger actions on event
- Summary, snapshot annotation, automatic deobfuscation
- Time measurement (CPU time, wall time)
- Snapshot directory customization
- Export of profiling results to HTML, CSV, XML, plain text
- Profiler API
- Profiler HTTP API
- Command line tool to control profiling
The so-called GC (Garbage Collector) roots are objects special for garbage collector. Garbage collector collects those objects that are not GC roots and are not accessible by references from GC roots.
There are several kinds of GC roots. One object can belong to more than one kind of root. The root kinds are:
- Class - loaded class. Classes can hold objects via static fields.
- Stack Local - local variable or parameter of method.
- Finalizer Queue Entry - object scheduled for finalization.
- GC Handle - provides a means for accessing a managed object from unmanaged memory.
- Other - objects hold from garbage collection by CLR for other reasons.
If an object is a root, it is specially marked in all views showing individual objects. For example, the following picture shows a fragment of paths view: