does not create a new line and consumes a lot of CPU resources

[intern]

Describe the bug

Local mac os system, using iterm2 to ssh connect to remote centos 7 system, ohmyzsh latest version installed on centos 7, encountering issues where pressing ctrl c does not create a new line, and zsh consumes a lot of CPU resources after the connection is disconnected.

Steps to reproduce

Local mac os system, using iterm2 to ssh connect to remote centos 7 system, ohmyzsh latest version installed on centos 7, encountering issues where pressing ctrl c does not create a new line, and zsh consumes a lot of CPU resources after the connection is disconnected.

Expected behavior

Rolling back to a previous version(15ffbdd) resolves the issue, and I haven't tested the versions in between. I'm not sure which version's changes are causing the problem.

Screenshots and recordings

No response

OS / Linux distribution

Mac os 13.52

Zsh version

5.9

Terminal emulator

iTerm2

If using WSL on Windows, which version of WSL

None

Additional context

Please Fix it!

[carlosala]

Could you git bisect and discover which commit creates the issue?

[intern]

ec1afe9

[intern]

Could you git bisect and discover which commit creates the issue?

This issue was caused by changes in this version. I noticed that "-t" was changed to "-T". After reverting this modification to "-t" on the master branch, the issue did not occur.

[carlosala]

@intern could you update to the latest omz master and see if it is fixed for you? Try it with no modifications and without disabling async prompt!

[liguoqinjim]

I encountered the same problem. Ctrl+C can still send an INT signal, but it cannot create a new line. Press Ctrl+C, then press a letter to create a new line.

[carlosala]

Hi @liguoqinjim! Which version of ohmyzsh are you running? Are you as well on centos 7?

[liguoqinjim]

Hi @liguoqinjim! Which version of ohmyzsh are you running? Are you as well on centos 7?
Hello, I tried it out and might have found the issue.I hope this helps you solve the problem.🤪

centos verions:CentOS Linux release 7.6.1810 (Core)
zsh version:zsh 5.0.2 (x86_64-redhat-linux-gnu)

correct commit: f78c6b9
commit that may have issues: 0c80a06

[mcornella]

If commit f78c6b9 fixes the issue then this is already solved in the latest version and this should be closed.

[mcornella]

Duplicate of #12331.

[liguoqinjim]

If commit f78c6b9 fixes the issue then this is already solved in the latest version and this should be closed.

Nope,the latest commit b1c5315a5fbc33624525e434ddbaec3bb30030e2still has the issue.

[mcornella]

And you can turn the behavior off with the following line in your .zshrc file, before Oh My Zsh is sourced?

zstyle ':omz:alpha:lib:git' async-prompt no

[mcornella]

Can you make a screen recording of the issue, and also put functions -t _omz_async_request _omz_async_callback in your zshrc file at the bottom to get a trace?

[liguoqinjim]

And you can turn the behavior off with the following line in your .zshrc file, before Oh My Zsh is sourced?

zstyle ':omz:alpha:lib:git' async-prompt no

commit id: "b1c5315a5fbc33624525e434ddbaec3bb30030e2"

zstyle ':omz:alpha:lib:git' async-prompt no
source $ZSH/oh-my-zsh.sh

With the line, result is correct.

[nasacj]

And you can turn the behavior off with the following line in your .zshrc file, before Oh My Zsh is sourced?

zstyle ':omz:alpha:lib:git' async-prompt no

This works. Could you please help to fix it? So that with runningomz update can fix this issue @mcornella

[carlosala]

Can you make a screen recording of the issue, and also put functions -t _omz_async_request _omz_async_callback in your zshrc file at the bottom to get a trace?

Could someone send the screen recording? 🙏🏻
Maybe @jsrdzhk?
Thanks!