Starting VS2022 Performance Profiler in "collection paused" mode

AndreyT 0 Reputation points
2026-03-19T22:07:41.47+00:00

VS2022 Performance Profiler can be started in "collection paused" mode{5CC49185-D8E7-48CD-AFE2-C9977C3414C6}

OK, it would indeed be useful to postpone collection of performance stats to a later point in program's execution. But how? How is this mode is supposed to be used? How do I "unpause" the collection after starting the program?

When I press the above "Start" button the program starts in "detached" mode, i.e. it is not controllable from Visual Studio. Breakpoints are ignored etc. So, again, how is this intended to work? How do I start collection of performance data?

Developer technologies | Visual Studio | Other
Developer technologies | Visual Studio | Other

A family of Microsoft suites of integrated development tools for building applications for Windows, the web, mobile devices and many other platforms. Miscellaneous topics that do not fit into specific categories.

0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest

  1. AI answer

    2026-03-19T22:07:54.4266667+00:00

    "Start with collection paused" only affects when the profiler begins recording data, not how the app is launched or debugged.

    When that option is checked and the Performance Profiler is started:

    1. Visual Studio launches the app under the selected profiling tool (for example, CPU Usage, .NET Object Allocation, Instrumentation) without immediately collecting data.
    2. The app runs normally, but profiling collection is paused.
    3. In the diagnostic session view that appears (the profiler report window), a Record button is available.
    4. When ready to begin collecting performance data (for example, after navigating past startup code), select Record. From that point on, the profiler records data.
    5. To stop collecting and see the report, select Stop collection (or close the app).

    This mode is intended for scenarios where startup behavior is not interesting and the focus is on a later portion of execution. It does not attach the debugger; the app runs without debugging while profiling.

    References:

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.