[Win7] possible crash when PresentMon process being killed about presentmon HOT 8 CLOSED

Thanks for reporting this; I'll take a look at what's going wrong.

Until I can find a fix, here are some potential workarounds:

• (obvious, but) don't kill PresentMon during that initial delay (e.g., if this is scripted)
• don't use -delay and prune the CSV file afterwards
• use the '-hotkey' instead of '-delay' to start the capture

from presentmon.

Besides, I have found that when PresentMon process is running, simply kill PresentMon process may cause the operating system suspended too. It is easy to reproduce this.

from presentmon.

I have not been able to reproduce this one. (Tested on Win10 16299.371)

If I kill PresentMon with Process Explorer or taskkill /F, PresentMon terminates immediately.

Sometimes if I kill PresentMon with unforced taskkill, PresentMon keeps running correctly but exiting with ctrl-c stops working. This one I can look at fixing, but I doubt this is what you meant by "operating system suspended".

Can you provide any more details on what you were doing to hit this and what you observed happen? If you have another computer, does it happen there too? Can you connect a (potentially remote) debugger?

from presentmon.

a7312fb65c6f1b9d498dc2b82e005d4c.zip

This is a video that shows "operating system suspended" at the 30th second.
This has been able to reproduce on 3 different computers, both in my company.

Microsoft Windows 7 Professional 6.1.7601 Service Pack 1 Build 7601
PresentMon64-1.3.1.exe

Another Win10 works fine.

I will continue to look for other computers to check if this is a common problem.

from presentmon.

I could understand if it only happens on Win7. The graphics kernel uses a different type of ETW on Win7 compared to Win8 and above. The more modern ETW can have 8 active listeners, while the older ETW can only have one - and I bet that if a session is created but events don't get processed, that bad things happen.

from presentmon.

Thank-you for the extra details and video.

Unfortunately I don't have a Win7 PC set up, and it may take me a while to test that.

Some other potential workarounds may be exiting PresentMon with:

• ctrl-c instead of closing the window
• using "-process_name" or "-process_id" along with "-terminate_on_proc_exit" and closing the target process.
• using "-terminate_after_timed -timed N" which will close PresentMon after N seconds.

from presentmon.

"-terminate_on_proc_exit" this may be a workaround and I will try it in my project. Thanks.
You may use a Virtual Machine to test in Windows 7 environment.

from presentmon.

Likely duplicate of #44. Believed fixed in master.

from presentmon.