From 621d1b03cd16849176d0d047107a9940fd6019cf Mon Sep 17 00:00:00 2001
From: Bartosz Taudul <wolf@nereid.pl>
Date: Fri, 21 May 2021 22:27:19 +0200
Subject: [PATCH] Update manual.

---
 manual/tracy.tex | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/manual/tracy.tex b/manual/tracy.tex
index 6fc358bb..afff202a 100644
--- a/manual/tracy.tex
+++ b/manual/tracy.tex
@@ -1531,6 +1531,10 @@ void DbgHelpUnlock() { ReleaseMutex(dbgHelpLock); }
 }
 \end{lstlisting}
 
+\paragraph{Disabling resolution of inline frames}
+
+Inline frames retrieval on Windows can be multiple orders of magnitude slower than just performing basic symbol resolution. This is being manifested as profiler seemingly being stuck for a long time, having hundred thousands of query backlog entries queued, which are slowly trickling down. If your use case requires speed of operation rather than having call stacks with inline frames included, you may define the \texttt{TRACY\_NO\_CALLSTACK\_INLINES} macro, which will make the profiler stick to the basic but fast frame resolution mode.
+
 \subsection{Lua support}
 
 To profile Lua code using Tracy, include the \texttt{tracy/TracyLua.hpp} header file in your Lua wrapper and execute \texttt{tracy::LuaRegister(lua\_State*)} function to add instrumentation support.