In the next version of .NET Memory Profiler we will make it possible to collect snapshots while debugging within Visual Studio. In the meantime, there is a workaround (a bit inconvenient though).
- Start profiling the application you want to investigate.
- Attach the Visual Studio debugger to the application. NOTE! For this procedure to work you must not attach the native debugger.
- When the debugger has stopped on a breakpoint, perform the following steps:
- In the "Threads" window, select all threads.
- Right-click on the threads and select "Freeze".
- Continue execution (F5)
- Collect a snapshot in the profiler.
- Break into the profiled process again by using Debug->Break All (Ctrl-Alt-Break).
- Select all threads again, right-click and select "Thaw".
- Now you have a snapshot at the location of the breakpoint that you just hit.
SciTech Software AB
Users browsing this forum: No registered users and 25 guests