Windows Profiler Utility

To clarify, this utility is for performance issues i.e. stalls, hangs, program "not responding", and slow responses, but not for crashes? What about the 'sudden crashes' that require the Event Viewer logs? Will the Profiler have an output without the Stop command?

Finally, does it replace diagnostic logging for problems/bugs?

Find more posts tagged with

Comments

Bradley Grainger (Logos)

To clarify, this utility is for performance issues i.e. stalls, hangs, program "not responding", and slow responses, but not for crashes?

Correct.

What about the 'sudden crashes' that require the Event Viewer logs?

Upload Event Viewer output, or use ProcDump.

Will the Profiler have an output without the Stop command?

No; is there a use case you're thinking of. (The only one I can think of is profiling shutdown of the application, but that's not a top priority for us right now.)

Finally, does it replace diagnostic logging for problems/bugs?

No. It augments diagnostic logging for performance bugs only.

Dave Hooton

https://community.logos.com/discussion/comment/900913#Comment_900913

Thanks for the helpful responses, Bradley.

Will the Profiler have an output without the Stop command?

No; is there a use case you're thinking of. (The only one I can think of is profiling shutdown of the application, but that's not a top priority for us right now.)

No; I wanted to clarify how the command works and thus confirm what it cannot be used for.