From 190809c990be254c171f93a37fa33cdfcccfeb87 Mon Sep 17 00:00:00 2001 From: Marcos Slomp Date: Thu, 10 Sep 2026 09:59:46 -0700 Subject: [PATCH] update docs --- NEWS | 5 +++++ manual/tracy.tex | 2 ++ server/TracyWorker.cpp | 1 + 3 files changed, 8 insertions(+) diff --git a/NEWS b/NEWS index 85b33f65..206f04a3 100644 --- a/NEWS +++ b/NEWS @@ -2,6 +2,11 @@ Note: There is no guarantee that version mismatched client and server will be able to talk with each other. Network protocol breakages won't be listed here. +vx.xx.x (2026-xx-xx) +-------------------- + +- Find zone window now works with GPU zones (histogram, statistics, self time). + v0.14.1 (2026-08-22) -------------------- diff --git a/manual/tracy.tex b/manual/tracy.tex index ef683ef7..8f9de006 100644 --- a/manual/tracy.tex +++ b/manual/tracy.tex @@ -4474,6 +4474,8 @@ Tracy gives you the ability to display an execution time histogram of all occurr You start by entering a search query, which will be matched against known zone names (see section~\ref{markingzones} for information on the grouping of zone names). If the search found some results, you will be presented with a list of zones in the \emph{matched source locations} drop-down. The selected zone's graph is displayed on the \emph{histogram} drop-down, and also the matching zones are highlighted on the timeline view. +GPU zones are supported as well, using their GPU execution time. Zone grouping, the found-zones list, and call stack samples are available only for CPU zones. + Clicking the \RMB{}~right mouse button on the source file location will open the source file view window (if applicable, see section~\ref{sourceview}). If symbol data is available Tracy will try to match the instrumented zone name to a captured symbol. If this succeeds and there are no duplicate matches, the source file view will be accompanied by the disassembly of the code. Since this matching is not exact, in rare cases you may get the wrong data here. To just display the source code, press and hold the \keys{\ctrl} key while clicking the \RMB{}~right mouse button. An example histogram is presented in figure~\ref{findzonehistogram}. Here you can see that the majority of zone calls (by count) are clustered in the 300~\si{\nano\second} group, closely followed by the 10~\si{\micro\second} cluster. There are some outliers at the 1~and~10~\si{\milli\second} marks, which can be ignored on most occasions, as these are single occurrences. diff --git a/server/TracyWorker.cpp b/server/TracyWorker.cpp index 1c84799a..de56a8e4 100644 --- a/server/TracyWorker.cpp +++ b/server/TracyWorker.cpp @@ -3600,6 +3600,7 @@ ThreadData* Worker::GetCurrentThreadData() int64_t Worker::GetGpuChildTime( const GpuEvent& zone ) const { + // Unresolved children (GpuEnd == -1, e.g. aborted trace) clamp to 0, overstating parent self-time. int64_t time = 0; if( zone.Child() >= 0 ) {