mirror of
https://github.com/wolfpld/tracy.git
synced 2026-11-17 05:05:58 +00:00
Calling matchActivityToAPICall in the MEMORY2 handler was consuming the cudaCallSiteInfo entry for the graph launch correlationId. If a graph mixes alloc nodes with kernel/memcpy nodes, all activities share the same correlationId — consuming it here would cause matchGraphActivityToAPICall to fail for the kernel/memcpy records that follow, silently dropping their GPU zones. Since apiCall is never used by the MEMORY2 handler (only address, size, and timestamp from the activity record are needed), remove the call entirely and leave the entry for the kernel/memcpy to consume and cache. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>