microsoft / terminal

The new Windows Terminal and the original Windows console host, all in the same place!
MIT License
95.27k stars 8.27k forks source link

Crash when creating a new tab #17046

Closed YisuiDenghua closed 5 months ago

YisuiDenghua commented 6 months ago

Windows Terminal version

1.19.10821.0

Windows build number

10.0.26085.0

Other Software

PowerShell 7.4.1

Steps to reproduce

Open the Windows Terminal on a non Administrator account, create a new tab.

Expected Behavior

No response

Actual Behavior

Faulting Application Name: WindowsTerminal.exe, Version: 1.19.2403.22001, Timestamp: 0x65fdabb8
Faulting module name: KERNELBASE.dll, version: 10.0.26085.1, timestamp: 0x0b2ecc91
Exception code: 0xc0000002
Fault offset: 0x00000000000cfc8a
Faulting process ID: 0x3BD0
Faulting application start time: 0x1DA8BFE9D0F5830
Faulting application path: C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.19.10821.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe
Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll
Report ID: 944f8d42-4feb-46a7-9c6e-6c024222006f
Faulting package full name: Microsoft.WindowsTerminal_1.19.10821.0_x64__8wekyb3d8bbwe
Faulting package relative application ID: App
github-actions[bot] commented 6 months ago

Hi I'm an AI powered bot that finds similar issues based off the issue title.

Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it. Thank you!

Closed similar issues:

Note: You can give me feedback by thumbs upping or thumbs downing this comment.

khkramer commented 6 months ago

I have the same issue. Although my log mentions a different DLL:

Faulting application name: WindowsTerminal.exe, version: 1.19.2403.22001, time stamp: 0x65fdabb8
Faulting module name: d2d1.dll, version: 10.0.19041.3636, time stamp: 0xa97c656e
Exception code: 0xc0000005
Fault offset: 0x00000000001355c2
Faulting process ID: 0x3a54
Faulting application start time: 0x01da8d7629b40d75
Faulting application path: C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.19.10821.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe
Faulting module path: C:\Windows\SYSTEM32\d2d1.dll
Report ID: c5a95475-bef9-4965-bc5a-46ca13ac1ba7
Faulting package full name: Microsoft.WindowsTerminal_1.19.10821.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App
zadjii commented 6 months ago

Do either of you have MacType installed? If you do, update to the latest version of MacType.

zadjii-msft commented 6 months ago

If not, can you file /feedback with the Feedback Hub, so that we can hopefully get a dump? Thanks!

etodanik commented 5 months ago

I also submitted feedback with this exact issue. Huge productivity killer.

I can confirm that turning off MacType stops it from crashing. But this is new, previous Terminal versions lived just fine with MacType

lhecker commented 5 months ago

@etodanik Please install the latest MacType version: https://github.com/snowie2000/mactype/releases/tag/v1.2023.5.31 The first bullet point in the changelog is what breaks Windows Terminal.

microsoft-github-policy-service[bot] commented 5 months ago

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment.