- "Profiler attach failed" error when attaching to a process in another container inside the same Kubernetes pod
- Profiling session takes a long time to start
- "Unable to start profiling. The system cannot find the file specified" error occurs if attach to ASP.NET Core 3.0 application when app pool's setting ".NET CLR version" is set to ".NET CLR Version v 4.0"
- "Unable to open the snapshot: Inconsistent call time values. This may be a result of CPU cores mistiming" error on opening a performance snapshot
- There may be no SQL events in a Timeline snapshot if it was taken during an attach session
- Incoming HTTP Requests events are not available for .NET Core applications profiled with Timeline profiling mode
- "Unknown call stacks" nodes in Timeline call tree view in case of profiling x64 applications in Windows 7 or earlier versions
- CLR 2.0 or earlier is not supported in Timeline profiling mode
- A snapshot obtained during Sampling profiling mode contains many unresolved nodes
- When profiling Windows Store application, stopping the application doesn't produce a snapshot
- Source code preview is sometimes not available while profiling unit tests