Terminal break down when I use python input() function.

c2ray commented 11 months ago

Windows Terminal version

Lastest

Windows build number

22H2

Other Software

python3

Steps to reproduce

https://github.com/microsoft/terminal/assets/55729509/2d370f4e-b987-40fa-a1f2-7f4f74930893

Expected Behavior

No response

Actual Behavior

It breaks down when I type something to python input() in windows terminal. It must be the keyword class.

zadjii-msft commented 11 months ago

Huh, looks like the IME caused the Terminal to crash there. That's sure weird, but I bet the feedback hub should be able to get a dump from the crash: /feedback

c2ray commented 11 months ago

Huh, looks like the IME caused the Terminal to crash there. That's sure weird, but I bet the feedback hub should be able to get a dump from the crash: /feedback

Submited feedback already.

zadjii-msft commented 11 months ago

Can you make sure to share the aka.ms link that's generated from the "Share" button/? It's effectively impossible for us to find it without a direct link 😕

c2ray commented 11 months ago

Can you make sure to share the aka.ms link that's generated from the "Share" button/? It's effectively impossible for us to find it without a direct link 😕

Here's the link, https://aka.ms/AAnl6wm.

zadjii-msft commented 11 months ago

Notes:

19045.3086.vb_release
"Windows Terminal version: latest" - well, that's not a real version. There's like 5 "latest" versions floating around in different channels.
RUNNING_PROCESS_INFO with tag IsTextInputManagementServiceRunning, { "Tag": "IsTextInputManagementServiceRunning=false" }

{
 "version": 7,
 "providerName": "Microsoft.Windows.Terminal.Win32Host",
 "hresult": "2147943809",
 "fileName": "C:\\__w\\1\\s\\src\\cascadia\\WindowsTerminal\\WindowEmperor.cpp",
 "lineNumber": "703",
 "module": "WindowsTerminal.exe",
 "failureType": "2",
 "message": "",
 "threadId": "12652",
 "callContext": "",
 "originatingContextId": "0",
 "originatingContextName": "",
 "originatingContextMessage": "",
 "currentContextId": "0",
 "currentContextName": "",
 "currentContextMessage": ""
}

Okay that's just a ERROR_HOTKEY_ALREADY_REGISTERED that's nothing

There are three crashes and they're only conhost so that's useless.
The error message about the text input service not running sure is curious but I don't know enough about how the IME works to investigate.

You might need to file feedback under a different area path, but I dont know what actually tracks the IME code 🤷

c2ray commented 11 months ago

Notes:
19045.3086.vb_release

"Windows Terminal version: latest" - well, that's not a real version. There's like 5 "latest" versions floating around in different channels.

RUNNING_PROCESS_INFO with tag IsTextInputManagementServiceRunning, { "Tag": "IsTextInputManagementServiceRunning=false" }
{
 "version": 7,
 "providerName": "Microsoft.Windows.Terminal.Win32Host",
 "hresult": "2147943809",
 "fileName": "C:\\__w\\1\\s\\src\\cascadia\\WindowsTerminal\\WindowEmperor.cpp",
 "lineNumber": "703",
 "module": "WindowsTerminal.exe",
 "failureType": "2",
 "message": "",
 "threadId": "12652",
 "callContext": "",
 "originatingContextId": "0",
 "originatingContextName": "",
 "originatingContextMessage": "",
 "currentContextId": "0",
 "currentContextName": "",
 "currentContextMessage": ""
}
Okay that's just a that's nothingERROR_HOTKEY_ALREADY_REGISTERED
There are three crashes and they're only conhost so that's useless.

The error message about the text input service not running sure is curious but I don't know enough about how the IME works to investigate.
You might need to file feedback under a different area path, but I dont know what actually tracks the IME code 🤷

I updated my windows terminal to 1.18.3181.0. It still appears.

lhecker commented 5 months ago

We just published a major update to our IME implementation in the nightly Canary branch. It was rewritten from the ground up and has tons of improvements! If you're interested in trying it out, you can get it here: https://aka.ms/terminal-canary-installer If you already have the Canary build installed, you can use this link to force an update.

If you encounter any issues or have any suggestions, or if you simply like/dislike the changes, please let us know! Thank you for bearing with us. 😊

lhecker commented 1 month ago

Please try Windows Terminal Preview v1.21 or later. As mentioned above, there's a new IME implementation. If the issue still occurs, let us know! Otherwise, the bot will close this issue in about a week. 🙂

microsoft-github-policy-service[bot] commented 1 month 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.

microsoft / terminal