b22c8e86ba
cudaMalloc/cudaFree (and driver equivalents) were tracked in cbidRuntimeTrackers/cbidDriverTrackers, creating a cudaCallSiteInfo entry on each API call. But the MEMORY2 handler never calls matchActivityToAPICall (and never calls EmitGpuZone) — it only needs the address, size, and timestamp from the activity record itself. Since no activity handler consumes these entries, they leaked indefinitely. Remove the 6 memory API CBIDs from both tracker maps so no entry is created. This eliminates the leak with no change in visible behavior: the MEMORY2 handler already operates independently of cudaCallSiteInfo. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
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++, Lua, Python and Fortran 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, Metal, OpenCL, CUDA.), 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
An Introduction to Tracy Profiler in C++ - Marcos Slomp - CppCon 2023
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