Basil Milanich b6222ae28b Fix MEMORY2 handler: don't gate memory tracking on API call correlation
CUpti_ActivityMemory3 has no graphId field, so graph-launched alloc
nodes and pre-profiling allocations can't be correlated to an API call.
The handler only needs address, size, and timestamp from the activity
record — apiCall is never used. Remove the early return so memory
tracking works in all cases.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
2026-04-07 15:33:41 -05:00
2026-03-02 23:58:16 +01:00
2024-05-25 00:16:29 +02:00
2024-05-12 19:23:18 +02:00
2026-01-24 01:50:11 +01:00
2023-10-09 22:38:04 +02:00
2022-04-16 00:13:10 +02:00
2026-01-24 01:50:11 +01:00
2026-03-02 20:35:23 +01:00
2025-12-11 23:46:02 +01:00
2026-03-19 19:53:58 +01:00
2025-07-27 21:18:57 +02:00
2025-07-12 11:50:11 +02:00
2024-09-27 16:56:55 +02:00
2026-01-01 02:12:05 +01:00
2026-01-30 21:49:17 +01:00

Tracy Profiler

Sponsor

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.

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

Description
No description provided
Readme BSD-3-Clause 105 MiB
Languages
C++ 89.8%
C 5.4%
TeX 2.4%
Python 1.1%
CMake 0.7%
Other 0.3%