Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
intern opened this issue Apr 17, 2024 · 4 comments
Open

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

intern opened this issue Apr 17, 2024 · 4 comments
Assignees

Comments

@intern
Copy link

intern commented Apr 17, 2024

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
Copy link
Member

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

@carlosala carlosala self-assigned this Apr 17, 2024
@intern
Copy link
Author

intern commented Apr 22, 2024

ec1afe9

@intern
Copy link
Author

intern commented Apr 22, 2024

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
Copy link
Member

carlosala commented Apr 22, 2024

@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!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Backlog
Development

No branches or pull requests

2 participants