mirror of
https://github.com/wolfpld/tracy
synced 2025-04-29 04:23:51 +00:00
2e9d8f8215
For some unknown reason, local threads may be attributed to an external process (at least when profiling on Windows). This causes some problems, for example the CPU usage graph may show that CPU is pegged by some other program, when it reality it is the profiled program that uses the CPU time. Workaround by checking first, if the thread id is known to be local by the profiler, i.e. if there were user-generated events originating from it. This still leaves other things, such as the CPU data list, being wrong, but the CPU data is meant to show raw TID -> PID mapping. If the source data is wrong, there's not much to fix here.
Tracy Profiler
A real time, nanosecond resolution, remote telemetry, hybrid frame and sampling profiler for games and other applications.
Tracy supports profiling CPU (Direct support is provided for C, C++, and Lua integration. At the same time, third-party bindings to many other languages exist on the internet, such as Rust, Zig, C#, OCaml, Odin, etc.), GPU (All major graphic APIs: OpenGL, Vulkan, Direct3D 11/12, OpenCL.), memory allocations, locks, context switches, automatically attribute screenshots to captured frames, and much more.
- Documentation for usage and build process instructions
- Releases containing the documentation (
tracy.pdf) and compiled Windows x64 binaries (Tracy-<version>.7z) as assets - Changelog
- Interactive demo
Introduction to Tracy Profiler v0.2
New features in Tracy Profiler v0.3
New features in Tracy Profiler v0.4
New features in Tracy Profiler v0.5
New features in Tracy Profiler v0.6
New features in Tracy Profiler v0.7
New features in Tracy Profiler v0.8