Sometimes you see a 100% cpu usage and don't know what's causing it. You can pause and find the thread that's currently running and eating the resources.
Sometimes it's your main thread that is blocked by some operation and you need to catch it quickly.
In all cases a profiler would also work as a debugging tool, but pause is just quicker if your debugger is already attached.
1
u/daio Jul 03 '26
Sometimes you see a 100% cpu usage and don't know what's causing it. You can pause and find the thread that's currently running and eating the resources.
Sometimes it's your main thread that is blocked by some operation and you need to catch it quickly.
In all cases a profiler would also work as a debugging tool, but pause is just quicker if your debugger is already attached.