search

Proryanator / encoder-benchmark

A tool to benchmark your hardware's real-time video encoding capabilities.
GNU General Public License v3.0
63 stars 5 forks source link

Crash when launching the benchmark #16

Closed TheWonderfulTartiflette closed 9 months ago

TheWonderfulTartiflette commented 1 year ago

i5-13500 with an Arc A770 Using the benchmark.exe, when asked if I want the verbose mode or not and answering, the cmd immediately closes, with no process happening in the background, and happens also when using the admin cmd as well

Proryanator commented 1 year ago

Thanks for opening the issue. Can you try opening a command prompt by hand and running it via ".\benchmark.exe"? That way the window won't close and we can see the error.

TheWonderfulTartiflette commented 1 year ago

Sorry for the late reply, but yes it works, only when opening it with the cmd and typing benchmark.exe

Proryanator commented 1 year ago

Hmm that's interesting, thanks for raising this. I'll make a note to look into what could be causing the crash.

TheWonderfulTartiflette commented 10 months ago

@Proryanator hey are there any updates on this?

Proryanator commented 10 months ago

@TheWonderfulTartiflette hey there! No updates yet but I can work on this ASAP!

Proryanator commented 9 months ago

@TheWonderfulTartiflette looking into this right now! May ping you if I have any questions.

Proryanator commented 9 months ago

@TheWonderfulTartiflette The tools could definitely use some work around better error handling and propagating but, in the mean time I've added in a catch all for any unhandled error to at least keep the cmd prompt open.

This should fix the issue of it just closing out without seeing any error.

Can you download this build and try again? Should be able to see the error that was thrown right before and help troubleshoot more. Appreciate you opening this though, highlighted some work that's needed for better error handling.

benchmark.zip

Proryanator commented 9 months ago

Going to go ahead and close this out as resolved. @TheWonderfulTartiflette do let me know if you still have issues and we can re-open this issue!