-
Notifications
You must be signed in to change notification settings - Fork 362
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
Memory leak? #5357
Comments
Hey @selkordy - thanks for letting us know! Definitely something very wrong here. I assume you've restarted Warp since then? If so, have you experienced runaway memory usage again? |
Yes I've restarted since and haven't seen such excessive memory usage. I have a hunch the problem is related to tqdm. I had many tqdms going with leave=False running a process that took days to run accumulating memory. |
Same here. It builds up when you leave it open. I've been using it daily for a couple weeks. |
Dupe Check
Describe the bug
Warp is using 100gb memory on my Mac. No doubt I've got a few tabs open but I only have a few remote SSH sessions going. It's leaking somewhere.
To reproduce
Not sure, but I've got ~8 tabs open with maybe ~15 panes
from top
ID COMMAND %CPU TIME #TH #WQ #PORT MEM PURG CMPRS PGRP PPID STATE
527 stable 5.3 04:09:56 73 3 461 101G+ 512M 76G- 527 1 sleeping
Expected behavior
No response
Screenshots
No response
Operating system
MacOS
Operating system and version
Sonoma 14.6.1 (23G93)
Shell Version
No response
Current Warp version
v0.2024.09.24.08.02.stable_01
Regression
Yes, this bug started recently or with an X Warp version
Recent working Warp date
Not sure, but I would have noticed a process using 100gb of memory. I believe this was introduced in the latest release.
Additional context
As of last week I did receive a few popups from my Mac that I was low on mem, but checking top nothing was using an excessive amount of memory and showed plenty of free memory available. I also received OOM errors in other apps. I now believe Warp has a memory leak.
Does this block you from using Warp daily?
No
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
The text was updated successfully, but these errors were encountered: