-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
Crash in main when writing settings to disk twice #10003
Comments
Looks like a @miniksa crash 😄 |
When I leave a breakpoint on the |
- Whenever we add a new profile setting from now on we have to update `Profile::CopySettings` _and_ `CascadiaSettings::DuplicateProfile` 👎 Notes from bug bash (checked bugs have been resolved): - [ ] The duplicate list can be very long if you have profiles - [x] DH: "Create new" seems too vague. "New empty profile" or something seems a little clearer to me. - [x] There is no deduplication counter for name - [x] Crash when your settings file is corrupt and we had to fall back to the defaults and you duplicate a profile - [x] Crash due to #10003 ## PR Checklist * [x] Closes #9121
Okay so I just tried this out and I could not get it to happen again. Maybe this fixed itself? I'm testing I was assuming that this was caused by the The original call stack I had for this crash was:
EDIT: Interesting. In the original stack, |
Nevermind. Found the specific repro. You absolutely must be on not the launch page. So yea, saving on a My guess as to what's happening - |
## Summary of the Pull Request Check for null before serializing the default terminal. Because the _currentDefaultTerminal is only initialized when the `Launch` page is navigated to, this _could_ be null if you navigate to another page, save, then save again. ## PR Checklist * [x] Closes #10003 * [x] I work here * [n/a] Tests added/passed * [n/a] Requires documentation to be updated ## Validation Steps Performed It crashed consistently before, it doesn't now.
🎉This issue was addressed in #10148, which has now been successfully released as Handy links: |
Windows Terminal version (or Windows build number)
main
Other Software
N/A
Steps to reproduce
Alternatively:
Expected Behavior
No crash
Actual Behavior
Terminal crashes. The crash seems to happen in the
Model::DefaultTerminal::Current(_currentDefaultTerminal);
call inCascadiaSettings::WriteSettingsToDisk()
, added in #9907The text was updated successfully, but these errors were encountered: