High CPU usage on MacOS Sequoia 15.3

Quen98 commented 2 weeks ago

Pre-submit Checks

[x] I have searched Warp bugs and there are no duplicates
[x] I have searched Warp known issues page and my issue is not there
[x] I have included the logs (optional, but helps expedite the bug fix). Log gathering intructions

Describe the bug

After upgrading to the latest stable version (v0.2025.06.18.08.11.stable_03), the app is taking a huge amount of CPU, heating up the device, and after a few commands become unresponsive: the input field can still be edited, but pressing enter does not work at all.

I'm using a 2021 14 inches MacBook Pro with specs:

Apple M1 Pro
16 gigs of RAM
Sequoia 15.3

warp-logs.zip

To reproduce

Not much, simply launching the app takes around 80-90% of the process. after a simple command like ls in the terminal the cpu usage goes to around 200%. After some usage the terminal becomes completely unresponsive, with a cpu usage around 400%.

Expected behavior

For Warp to use a decent amount of CPU, and the execute terminal commands upon enter key pressed

Screenshots, videos, and logs

No response

Operating system (OS)

macOS

Operating system and version

Sequoia 15.3

Shell Version

zsh 5.9 (arm64-apple-darwin24.0)

Current Warp version

v0.2025.06.18.08.11.stable_03

Regression

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

Recent working Warp date

No response

Additional context

No response

Does this block you from using Warp daily?

Yes, this issue prevents me from using Warp daily.

Is this an issue only in Warp?

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

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

None

Quen98 commented 2 weeks ago

Here's the unresponsive issue in video:

https://github.com/user-attachments/assets/a7d9e387-8688-4d90-a3b2-72cdd5aab149

kevinyang372 commented 2 weeks ago

@Quen98 Hi! Sorry for the experience here. If you turn off codebase context feature under the code tab, does this help with the CPU usage issue by any chance?

Quen98 commented 2 weeks ago

Hey Yunfan ! Thanks for reaching back quickly. Unfortunately not, I turned off codebase indexing, but Warp still takes 200% of cpu, even after killing and reopening the app

eugenejeonme commented 2 weeks ago

I'm having a similar issue. I turned off the codebase indexing feature. But it didn't help. I hope the cause is found out or fixed soon.

Quen98 commented 2 weeks ago

Upgrading to v0.2025.06.20.22.47.stable_05 seems to resolve the issue

kevinyang372 commented 2 weeks ago

Yeah we pushed an update that fixes this. Thanks for reporting!

warpdotdev / Warp