Warp hangs on command execution when Covalence is installed

Open
#3,820 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
macos, rust, zsh

Research direction

No source file, test, or code entry point is identified. First reproduce pwd in Warp v0.2023.10.17.08.03 on macOS 14.1 with zsh 5.9 and Covalence installed, then compare with another terminal; done means command execution no longer takes about 22 seconds or causes CPU spikes.

Written by the indexing model from the issue text.

Description

bug ready-to-implement triaged
Discord username (optional)

No response

Describe the bug

After installing the latest update for warp, the terminal become not usable.
Any execution of command is extremely slow and causes spikes in cpu usage (even disables the Bluetooth temporarily ) .

After a couple of hours of investigation, i cannot find a root cause, what i've tried already:

  • Re-installing warp
  • Uninstall omz and all related files
  • Re-installing xcode
  • Updating all of the packages
  • Re-install git (brew/mac)
  • I don't have any nvm installed

For example:
Execution of pwd takes 22 seconds and in the end it causes CPU spike.

Would appreciate any advice, thank you!

To reproduce

Open warp latest version -> execute command

Expected behavior

Not having performance issues

Screenshots

No response

Operating system

MacOS

Operating system and version

14.1 (23B74

Shell Version

zsh 5.9 (x86_64-apple-darwin23.0)

Current Warp version

v0.2023.10.17.08.03.stable_02

Regression

No, this bug or issue has existed throughout my experience using Warp

Recent working Warp date

30-10-2023

Additional context

I do have installed covalen and jumpcloud - maybe it somehow relaeted

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:b8107fdf-ba31-488d-b103-d271c89cac3e

None

Dominant language
Rust
Stars
65.1k
Forks
5.6k
PR merge metrics
PR metrics pending

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from warpdotdev/warp

All issues in warpdotdev/warp

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.