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

Terminal Slow Reacting and can't quit from panel. #4933

Open
1 task done
popfido opened this issue May 19, 2024 · 3 comments
Open
1 task done

Terminal Slow Reacting and can't quit from panel. #4933

popfido opened this issue May 19, 2024 · 3 comments
Labels
Bugs Bugs, Hangs, Crash, and Freezes

Comments

@popfido
Copy link

popfido commented May 19, 2024

Dupe Check

Describe the bug

The reacting time of each operation becomes quite long and can't quite Warp Terminal through ordinary way. I can just close Warp from Activity Monitor with force quit.

To reproduce

  1. Open Warp Terminal
  2. Wait for some time

Expected behavior

terminal react at a very quick speed and can exit.

Screenshots

image image

Operating system

MacOS

Operating system and version

14.5 (23F79)

Shell Version

zsh 5.9 (x86_64-apple-darwin23.0)

Current Warp version

v0.2024.05.07.08.02.stable_02

Regression

Yes, this bug started recently or with an X Warp version

Recent working Warp date

2 months earlier

Additional context

No response

Does this block you from using Warp daily?

Yes, this issue prevents me from using Warp daily.

Is this a Warp specific issue? (i.e. does it happen in Terminal, iTerm, Kitty, etc.)

Yes, this I confirmed this only happens in Warp, not other terminals.

Warp Internal (ignore): linear-label:b9d78064-c89e-4973-b153-5178a31ee54e

None

@popfido popfido added the Bugs Bugs, Hangs, Crash, and Freezes label May 19, 2024
@anggerpr
Copy link

I also experienced almost the same thing, the command execution did not start immediately when I pressed enter, I had to press the enter key several times.

@popfido
Copy link
Author

popfido commented May 20, 2024

I also experienced almost the same thing, the command execution did not start immediately when I pressed enter, I had to press the enter key several times.

For me the problem is even more severe that I, not only need to press the enter key several times, but also not sure how long is the response time after I pressed and whether the command truly effects. Currently I don't have an accurate way to stably reproduce this bug but it just keep emerging.

@dannyneira
Copy link
Member

Hey folks, my guess is that you normally have a custom prompt, theme, or bash/zsh/fish plugin and Warp is unable to parse it.

You can check whether it’s something in your dotfiles by setting up clean configs:
Run echo 'ZDOTDIR=/' > ~/.zshenv
This forces Zsh to run with zero configs.

We have a list of incompatible tools here: https://docs.warp.dev/help/known-issues#list-of-incompatible-tools
You can disable parts of your dotfiles just for Warp by using this conditional statement:

# Bash and Zsh
if [[ $TERM_PROGRAM != "WarpTerminal" ]]; then
# > What you want to disable here <
fi

If commenting out the rc files doesn't help with the slow issues please let us know and provide copy of the logs. https://docs.warp.dev/help/sending-us-feedback

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bugs Bugs, Hangs, Crash, and Freezes
Projects
None yet
Development

No branches or pull requests

3 participants