New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MaxTo crashes when viewing regions and exiting "cancel changes" #635
Comments
Thank you for reporting this. This seems to be the stack trace that caused your issue:
Is this reproducible consistently on your machine? What are the exact steps you take to make it crash like this? |
I can reproduce it again and again. BTW: Where should I find the stack trace. It could be this. There's Dutch tekst in it. |
After restoring my last config.json (before upgrade). Problem solved |
Thank you for reporting this. It was something that only happens on multi-monitor solutions, and since Covid I've been on a single-monitor system, which is why I didn't catch this. I dug out an old monitor and was able to reproduce it. The fix will be in 2.1.1. |
First of all, after installing 2.1.0. Stable over 2.1 beta 5. My own region are vanished.
When I look at te regions, press on presets. I don't see, my own.
Clicking on [Cancel changes] make MaxTo crash.
Restart MaxTo.Core, says there was a crash.
Starting again tells me MAxTo is already runnig. I don't see anything in the notification area, nor in the task manager, but procesexplorer does.
maxto20201030.log
The text was updated successfully, but these errors were encountered: