Torbjørn Viem Ness

The tricky part about this is that it's not 100% reproducible, but it's happened often enough that I'm fairly certain it's the same issue. I have captured Event Log files...

Event log details from the crash today: ```xml 1000 0 2 100 0 0x80000000000000 157500 Application removed WindowsTerminal.exe 1.13.2205.23001 628bd6e7 Microsoft.Terminal.Control.dll 1.13.2205.23001 628bd51b c0000005 00000000000c1622 6120 01d895c3d9743c03 C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.13.11431.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe C:\Program...

I tried recording using the Feedback Hub earlier, but for some reason it wouldn't start (also I guess it'd have to be recording until the issue happened, so that could...

It crashed again just now, but no dumps were found in the AppData\Local folder, not even the CrashDumps folder itself - do you have to create that manually first for...

Just to keep the bots happy, I guess I can comment. Glad to see that you guys were able to reproduce it so I'm not the only one, should hopefully...

Great to see that this issue has been reproduced in different ways by several independent reporters, and especially that it's been assigned to a milestone! I've started to see a...

Happened again with new version: 1.14.2281.0 (updated after the previous comment I made) Event log: ``` Faulting application name: WindowsTerminal.exe, version: 1.14.2208.16001, time stamp: 0x62fc1924 Faulting module name: Microsoft.Terminal.Control.dll, version:...

Sorry about the necroposting, I was just browsing and saw the "help wanted" tag. :) About the parameters, I think it's good to have all default values be set from...

I guess this also works with 64 bit accesses even though only 32 bit registers are specified (maybe there should be a note about this to remove ambiguity)? I like...

Any updates on this? Terminal has crashed 3 times today (in about 3 hours) so it's getting pretty annoying... Happy to test beta versions with a suggested fix or anything...