Our internal trace recording tool has an optional input event logger which puts all keyboard and mouse input into the trace (watch for it). Look for patterns in the CPU usage or other data.Use instrumentation in the functions of interest.Find the key stroke that triggered the hang, through logging of input events.A trace might cover 60 seconds, and a hang might last for 2 seconds or less, so knowing where to look is crucial. It is sufficiently simple and self-contained that I can cover it end-to-end in a single (long) post.įinding the hang When profiling a transient problem such as a frame-rate glitch or a temporary hang the first challenge is to locate the hang in the trace. The last investigation is the one I want to cover today. Finding the cause of (and a workaround for) repeated 2-6 second hangs in Visual Studio's output window. ![]() ![]()
0 Comments
Leave a Reply. |