-
Notifications
You must be signed in to change notification settings - Fork 30
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
Stabilize connections and automatic restarts/recoveries #31
Comments
I have started and stopped the app about twenty times and one device failed to start on about three of those starts. I ran Resource Monitor throughout and I did not see excessive CPU or memory use. I did not see that any values in Resource Monitor were different when a device failed to start. I cannot see any common factor in the fails. I haven't a clue. |
In 1.9.68 I do a retry when 'load failed'. Maybe that works!? |
Started 15 times and the devices all started on each and every startup ... but they were not in sync ... Logs 029 and 030 Windows resizing works well ... thank you. Restart last used group worked well ... I did not try restart last used devices. Thank you again. Start when Windows starts kinda worked ... The app starts but gives an exceptions ... Logs 031 and 032 ... Overall a solid B |
I dropped the wrong file 😄, this is the real Setup 1.9.68.zip with the retry fix. Can you try that one as well? (Then I can make that version 2.0.) I already started with the 2.0 issues in another branch. Odd that all devices started now, I don't think I changed anything there in the 2.0 branch. |
1.9.68 033 - All devices started but not in sync Is it only me that has a problem with automatic start of all devices? It may be that the problem is specific to my setup. I will never use automatic start of all devices so it may be that you don't need to chase this problem if it is only me. I expect that somebody that wants to automatically start all devices will be able to test this in future if you make any further changes. |
It's retrying, but it doesn't fix the connection. |
The text was updated successfully, but these errors were encountered: