Crash - Illegal characters in path.

[chrisheinonen]

Describe the bug
New install on a new laptop, has updated to 4.8.5. As soon as I click on Start Response Time Testing I get a pop-up of "Unexpected Error: Illegal Characters in Path"

To Reproduce
Steps to reproduce the behavior:

1. Click 'Start Response Time Testing'
2. Get error

Expected behavior
Response time testing should start

Screenshots
NA

Desktop (please complete the following information):

• OS: Windows 11 ARM
• Version 4.8.5
• Display - 2880x1800, 60Hz, no HDR, 200% scaling

Additional context
Add any other context about the problem here.

Supporting Files
OSRTT Crashes.evtx.zip

Windows Event Viewer events attached

[andymanic]

Hi Chris, thanks for the bug report! I am yet to use Windows 11 ARM so I have to assume it's something going on there - the crash seems to be from when the program tries to create a folder for the results - can you let me know what the monitor name reports as in the main window, and if you are including any special overdrive mode text?

[chrisheinonen]

The monitor name reports as "134WT1" and it crashes before the pop-up window that lets me select an Overdrive Mode or enter a custom one.

[andymanic]

OSRTT Launcher.zip
I've just whipped up a test version of the app (that I had to zip up to be able to link here) - can you run that and screenshot/copy what the message box includes when you hit start test?

[chrisheinonen]

[andymanic]

I'm surprised this is the first time that has happened! It seems the WindowsAPI I use for getting the monitor name is adding a new line to the name, which is breaking the search function. I'll fix that and send over a new version for you and include the fix in all future releases too.

[andymanic]

OSRTT Launcher.zip
This should be a fix for that - please do let me know if it doesn't work as I am unable to replicate the issue locally so can't test to make sure!

[chrisheinonen]

"Object reference not set to an instance of an object"

Event Viewer files attached. This time the Overdrive Mode window does launch, but as soon as it does the above error occurs. This didn't happen on other ARM laptops so must be something strange about this one.

OSRTT Crashes 2.zip

[andymanic]

OSRTT Launcher.zip
I suspect my fix didn't quite get it - here's a version with that message box put back in but the remove new line still there. Can you show me what the message box says again? I'm trying to work out how I can replicate the issue to test it locally but I'm drawing a blank!