-
Notifications
You must be signed in to change notification settings - Fork 137
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
Fix crash when window is closed while thread running #685
Conversation
Takes up about 6-10MB more memory when window closed. |
Sounds good. You want to do a PR for those changes, since you already have them working? I'll test on macOS. |
This is the pull request.
|
Another solution is making the parent of the threads VortaApp. Downsides: |
Went with the alternate method of fixing it, see comment above. Might undo it later, since I'm still on the fence about it. Closing and opening the window clears the messages. Going to fix that. Would be easier to keep the messages using original method. |
I also think that keeping the window state would have benefits. |
Tested on macOS. Didn't see any issues. Actually nice to keep the window state when reopening it. |
I've decided to both keep the window state, and correctly set the borg thread parents. Technically the second one is not needed, but its nice to have. |
Merged. I like it how window state, logs, etc are preserved. Good change! |
Fixes #684
I only opened the issue to confirm that it wasn't a weird setup issue, since I remember this not crashing in the past.
Opening and closing the window is so much faster now, as an upside.
Check to make sure this doesn't reintroduce #340, doesn't in my testing.