-
Notifications
You must be signed in to change notification settings - Fork 8.4k
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
Deleting a (last?) profile in the SUI sends the Terminal to a farm upstate #13017
Comments
I cannot repro this on current main nor on preview (1.14.891.0). Do you consistently hit this or only sometimes? |
Okay, got it to hit the second time I tried this. First time, no repro. Second time, I made the Terminal wide enough that the nav view was in its expanded state, and then the terminal died on the delete. |
Gosh I can't find it now, but we had some crash in the past about changing the elements of a nav view. Something about the vector of items.... @carlos-zamora do you remember what I'm thinking of? |
// Add an event handler for when the user wants to delete a profile.
profile.DeleteProfile({ this, &MainPage::_DeleteProfile }); I'd bet we're adding the delete handler TWICE. Stepping through It might mean that the repro is
|
Turns out if you add that Delete handler there, then every time you navigate to the profile, we'll add another Delete handler to the list of handlers. That's bad - that'll cause us to try and delete the profile multiple times. The repro I had before was 100%, now it's fixed. * [x] Closes #13017
Turns out if you add that Delete handler there, then every time you navigate to the profile, we'll add another Delete handler to the list of handlers. That's bad - that'll cause us to try and delete the profile multiple times. The repro I had before was 100%, now it's fixed. * [x] Closes #13017 (cherry picked from commit d072314) Service-Card-Id: 81599094 Service-Version: 1.14
Turns out if you add that Delete handler there, then every time you navigate to the profile, we'll add another Delete handler to the list of handlers. That's bad - that'll cause us to try and delete the profile multiple times. The repro I had before was 100%, now it's fixed. * [x] Closes #13017 (cherry picked from commit d072314) Service-Card-Id: 81744856 Service-Version: 1.13
🎉This issue was addressed in #13044, which has now been successfully released as Handy links: |
🎉This issue was addressed in #13044, which has now been successfully released as Handy links: |
Stack was useless - something above a
DispatcherLoop
with aReportUnhandledError
about a "The application attempted to access data outside the valid range" but I apparently don't have!xamlstowed
installed anymore.The text was updated successfully, but these errors were encountered: