Terminal crashes when opening Settings #18050

@zadjii-msft commented on GitHub (Jul 27, 2022):

Are you running on an ARM PC by any chance? A Feedback Hub trace of the crash might be helpful: /feedback

@zadjii-msft commented on GitHub (Jul 27, 2022): Are you running on an ARM PC by any chance? A Feedback Hub trace of the crash might be helpful: /feedback

claunia commented

@ghost commented on GitHub (Jul 27, 2022):

Hi there!

Can you please send us feedback with the Feedback Hub with this issue? Make sure to click the "Start recording" button, then reproduce the issue before submitting the feedback. Once it's submitted, paste the link here so we can more easily find your crash information on the back end?

Thanks!

@ghost commented on GitHub (Jul 27, 2022): Hi there! Can you please send us feedback with the [Feedback Hub](https://support.microsoft.com/en-us/windows/send-feedback-to-microsoft-with-the-feedback-hub-app-f59187f8-8739-22d6-ba93-f66612949332) with this issue? Make sure to click the "Start recording" button, then reproduce the issue before submitting the feedback. Once it's submitted, paste the link here so we can more easily find your crash information on the back end? Thanks! ![image](https://user-images.githubusercontent.com/18356694/140811502-a068f78b-89d2-4587-925a-73e19652b830.png) ![image](https://user-images.githubusercontent.com/18356694/140811557-cdc22a0f-fa6a-4f6a-953e-73b51f5548a3.png) ![image](https://user-images.githubusercontent.com/18221333/62478649-6de55400-b760-11e9-806e-5aab7e085a9f.png)

claunia commented

@GoodBoyNeon commented on GitHub (Jul 27, 2022):

https://aka.ms/AAhkd1t That's the link of the feedback. Thanks for your support!

@GoodBoyNeon commented on GitHub (Jul 27, 2022): https://aka.ms/AAhkd1t That's the link of the feedback. Thanks for your support!

claunia commented

@zadjii-msft commented on GitHub (Jul 27, 2022):

Did you actually capture a recording of the crash with Feedback Hub? I'm not seeing any dumps in the backend, but it's also entirely possible that they just haven't had the time to fully propagate yet...

@zadjii-msft commented on GitHub (Jul 27, 2022): Did you actually capture a recording of the crash with Feedback Hub? I'm not seeing any dumps in the backend, but it's also entirely possible that they just haven't had the time to fully propagate yet...

claunia commented

@zadjii-msft commented on GitHub (Jul 27, 2022):

... Yea okay there comes some more data. Looks like the backend is just chugging a little slowly today.

@zadjii-msft commented on GitHub (Jul 27, 2022): ... Yea okay there comes some more data. Looks like the backend is just chugging a little slowly today.

claunia commented

@zadjii-msft commented on GitHub (Jul 28, 2022):

Hmm. The FH dump doesn't have a terminal dump in it, but it does link to an exception in MTSM.dll, ExceptionCode=3221225477, ExceptionOffset=164756. 3221225477 is ERROR_ACCESS_DENIED, which is peculiar. Curious that the blame was on MTSM.dll, and not MTSE.dll.

(there is a ERROR_INVALID_PARAMETER logged from MTSM, but that's just the icon converter, which like, whatever)

OP was not on ARM

@zadjii-msft commented on GitHub (Jul 28, 2022): Hmm. The FH dump doesn't have a terminal dump in it, but it does link to an exception in MTSM.dll, `ExceptionCode=3221225477, ExceptionOffset=164756`. `3221225477` is `ERROR_ACCESS_DENIED`, which is peculiar. Curious that the blame was on MTSM.dll, and not MTSE.dll. (there is a `ERROR_INVALID_PARAMETER` logged from MTSM, but that's just the icon converter, which like, whatever) **OP was not on ARM**

claunia commented

@zadjii-msft commented on GitHub (Aug 10, 2022):

By any chance was the settings.json file open in another editor when you tried this? Or did you save the file while the settings UI was open/? Just feeling bits of #13673 here.

@zadjii-msft commented on GitHub (Aug 10, 2022): By any chance was the settings.json file open in another editor when you tried this? Or did you save the file while the settings UI was open/? Just feeling bits of #13673 here.

claunia commented

@GoodBoyNeon commented on GitHub (Aug 11, 2022):

No, I wasn't opening the settings.json while trying that. I am not sure about if I saved the json file while the UI was open. I tried re installing though but it still crashes

@GoodBoyNeon commented on GitHub (Aug 11, 2022): No, I wasn't opening the settings.json while trying that. I am not sure about if I saved the json file while the UI was open. I tried re installing though but it still crashes

claunia commented

@TJSC1213 commented on GitHub (Aug 17, 2022):

I have the same problem at all,and the version of my terminal on my windows10 is 10.0.19044.1889

@TJSC1213 commented on GitHub (Aug 17, 2022): I have the same problem at all,and the version of my terminal on my windows10 is 10.0.19044.1889

claunia commented

@zadjii-msft commented on GitHub (Aug 17, 2022):

@TJSC1213 can you submit feedback in the same way I requested above? More data might help ID the root cause here.

@zadjii-msft commented on GitHub (Aug 17, 2022): @TJSC1213 can you submit feedback in the same way [I requested above](https://github.com/microsoft/terminal/issues/13610#issuecomment-1196586320)? More data might help ID the root cause here.

claunia commented

@salastro commented on GitHub (Oct 4, 2022):

I have the exact same problem.

@salastro commented on GitHub (Oct 4, 2022): I have the exact same problem.

claunia commented

@thals1992 commented on GitHub (Dec 26, 2022):

I found that I have the same issue. I tried resetting the app as well as uninstalling the app via settings and reinstalled it from the Microsoft Store. It's running on Win 10 22H2, but the 32-bit version on my Dell Venue 8 Pro.

@thals1992 commented on GitHub (Dec 26, 2022): I found that I have the same issue. I tried resetting the app as well as uninstalling the app via settings and reinstalled it from the Microsoft Store. It's running on Win 10 22H2, but the 32-bit version on my Dell Venue 8 Pro.

claunia commented

@zadjii-msft commented on GitHub (Jan 3, 2023):

Can you submit feedback in the same way I requested above? More data might help ID the root cause here.

@zadjii-msft commented on GitHub (Jan 3, 2023): Can you submit feedback in the same way [I requested above](https://github.com/microsoft/terminal/issues/13610#issuecomment-1196586320)? More data might help ID the root cause here.

claunia commented

@shawn99452 commented on GitHub (Jan 19, 2023):

This occurs on my Windows 10 22H2 32-bit PC also, running Windows Terminal 1.15.3465.0. Changes made in settings.json externally take effect in Terminal, so it's reading the file ok, but any attempt to open the Settings UI from inside Terminal causes it to freeze for a second, close the dropdown menu, freeze a few more seconds, and then exit Terminal entirely. Renaming the settings.json file causes it to make a new one on startup, but the crash when opening the Settings UI still occurs with the default settings.
WindowsTerminal.exe.10184.dmp.zip

@shawn99452 commented on GitHub (Jan 19, 2023): This occurs on my Windows 10 22H2 32-bit PC also, running Windows Terminal 1.15.3465.0. Changes made in settings.json externally take effect in Terminal, so it's reading the file ok, but any attempt to open the Settings UI from inside Terminal causes it to freeze for a second, close the dropdown menu, freeze a few more seconds, and then exit Terminal entirely. Renaming the settings.json file causes it to make a new one on startup, but the crash when opening the Settings UI still occurs with the default settings. [WindowsTerminal.exe.10184.dmp.zip](https://github.com/microsoft/terminal/files/10459426/WindowsTerminal.exe.10184.dmp.zip)

claunia commented

@zadjii-msft commented on GitHub (Jan 19, 2023):

Can you submit feedback in the same way I requested above? More data might help ID the root cause here.

@zadjii-msft commented on GitHub (Jan 19, 2023): > Can you submit feedback in the same way [I requested above](https://github.com/microsoft/terminal/issues/13610#issuecomment-1196586320)? More data might help ID the root cause here.

claunia commented

@shawn99452 commented on GitHub (Jan 19, 2023):

Can you submit feedback in the same way I requested above? More data might help ID the root cause here.

Trying to, but the Feedback Hub app just shows a blank screen with spinning dots forever when I click "Report a Problem". Every page in Feedback Hub except the 'Feedback' page works fine :(. I'll edit my original note, adding the link, if I get it to work. Is there another way to get the requested data, outside Feedback Hub?

@shawn99452 commented on GitHub (Jan 19, 2023): > > Can you submit feedback in the same way [I requested above](https://github.com/microsoft/terminal/issues/13610#issuecomment-1196586320)? More data might help ID the root cause here. Trying to, but the Feedback Hub app just shows a blank screen with spinning dots forever when I click "Report a Problem". Every page in Feedback Hub except the 'Feedback' page works fine :(. I'll edit my original note, adding the link, if I get it to work. Is there another way to get the requested data, outside Feedback Hub?

claunia commented

@zadjii-msft commented on GitHub (Jan 19, 2023):

Wow what fortuitous timing that I just wrote up: Capturing and sending dumps

@zadjii-msft commented on GitHub (Jan 19, 2023): Wow what fortuitous timing that I just wrote up: [Capturing and sending dumps](https://github.com/microsoft/terminal/wiki/Toubleshooting-Tips#capturing-and-sending-dumps)

claunia commented

@zadjii-msft commented on GitHub (Apr 28, 2023):

Hmm, this is the one that I thought might be related to #15243 but ultimately the two are so different, I can't imagine they've got the same root cause.

It does seem like it's a consistent theme that you're all on 32-bit Windows. That's definitely curious. I wonder if I can even get this to repro in a 32-bit VM on a 64bit

HEY LOOK 9 YEARS LATER, SYMBOLS LOADED

SYMBOL_NAME:  microsoft_terminal_settings_model!`winrt::Microsoft::Terminal::Settings::Model::implementation::CascadiaSettings::_refreshDefaultTerminals'::`2'::<lambda_1>$_ResumeCoro$1::operator+137

MODULE_NAME: Microsoft_Terminal_Settings_Model

IMAGE_NAME:  Microsoft.Terminal.Settings.Model.dll

STACK_COMMAND:  ~15s; .ecxr ; kb

FAILURE_BUCKET_ID:  NULL_CLASS_PTR_READ_c0000005_Microsoft.Terminal.Settings.Model.dll!_winrt::Microsoft::Terminal::Settings::Model::implementation::CascadiaSettings::_refreshDefaultTerminals_::_2_::_lambda_1_$_ResumeCoro$1::operator

OS_VERSION:  10.0.19045.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x86

OSNAME:  Windows 10

IMAGE_VERSION:  1.15.2212.12005

FAILURE_ID_HASH:  {c5fe23d8-68c6-0750-b26c-7605d5cc7af0}

@zadjii-msft commented on GitHub (Apr 28, 2023): Hmm, this is the one that I thought might be related to #15243 but ultimately the two are so different, I can't imagine they've got the same root cause. It does seem like it's a consistent theme that you're all on 32-bit Windows. That's definitely curious. I wonder if I can even get this to repro in a 32-bit VM on a 64bit HEY LOOK 9 YEARS LATER, SYMBOLS LOADED ``` SYMBOL_NAME: microsoft_terminal_settings_model!`winrt::Microsoft::Terminal::Settings::Model::implementation::CascadiaSettings::_refreshDefaultTerminals'::`2'::<lambda_1>$_ResumeCoro$1::operator+137 MODULE_NAME: Microsoft_Terminal_Settings_Model IMAGE_NAME: Microsoft.Terminal.Settings.Model.dll STACK_COMMAND: ~15s; .ecxr ; kb FAILURE_BUCKET_ID: NULL_CLASS_PTR_READ_c0000005_Microsoft.Terminal.Settings.Model.dll!_winrt::Microsoft::Terminal::Settings::Model::implementation::CascadiaSettings::_refreshDefaultTerminals_::_2_::_lambda_1_$_ResumeCoro$1::operator OS_VERSION: 10.0.19045.1 BUILDLAB_STR: vb_release OSPLATFORM_TYPE: x86 OSNAME: Windows 10 IMAGE_VERSION: 1.15.2212.12005 FAILURE_ID_HASH: {c5fe23d8-68c6-0750-b26c-7605d5cc7af0} ```

claunia commented

dec420eb42/src/cascadia/TerminalSettingsModel/CascadiaSettings.cpp (L1122-L1145)

@zadjii-msft commented on GitHub (Apr 28, 2023):

Well, the dump thinks L1139 is the failure here:

I'm pretty confident we're in "wacky undefined compiler bug with coroutines and x86" territory here.

There's also no dumps of this on the backend, which is curious.

@zadjii-msft commented on GitHub (Apr 28, 2023): Well, the dump thinks L1139 is the failure here: https://github.com/microsoft/terminal/blob/dec420eb422a0cac51ab5b1d02ad73b99db4d2bb/src/cascadia/TerminalSettingsModel/CascadiaSettings.cpp#L1122-L1145 I'm pretty confident we're in "wacky undefined compiler bug with coroutines and x86" territory here. There's also _no_ dumps of this on the backend, which is curious.

claunia commented