Warp
Warp copied to clipboard
warpdotdev
High Memory Usage
Discord username (optional)
No response
Describe the bug
Warp uses a significant amount of memory for a terminal. After using it for a day with 3-5 tabs open (sometimes closing and sometimes opening new ones):
After I close all tabs memory drops in half but is still 200MB
To Reproduce
Use Warp with multiple tabs.
Expected behaviour
Better memory management. When closing all tabs, memory should reduce to the lower (but still surprisingly high) 100MB which is what happens on start.
Screenshots
No response
Operating System
None
OS Version
Monteray 12.5.1
Shell Version
zsh 5.8.1 (x86_64-apple-darwin21.0)
Warp Version
v0.2023.01.31.08.08.stable_02
Additional context
No response
Does this block you from using Warp daily?
No
Warp Internal (ignore): linear-label:b8107fdf-ba31-488d-b103-d271c89cac3e
None
Thanks for letting us know, by any chance are you using any unsupported plugins in your rc files?
https://docs.warp.dev/help/known-issues#configuring-and-debugging-your-rc-files
I have oh-my-zsh enabled but I have just disabled it and will see how it goes.
Just to chime in.
Using the latest v0.2023.02.21.08.03.stable_01, I get 300MB memory usage freshly launched doing nothing.
Kinda insane it uses more RAM than say Hyper, a terminal app build in Electron, which is supposedly as bad as it goes.
I have been running Warp on my Mac for a few weeks now with 20-30 tabs and it is now using 7G. I really don't want to have to close it to free that up. Maybe add an option to clear all blocks for all tabs or something?
Thanks for the feedback! Warp's memory consumption is something I'm working on; there should be some improvements to memory usage in the release coming out this Thursday, but there's certainly a lot more work we can do to improve things.
@davidtinker It's not as convenient as a "clear all blocks for all tabs" option, but you can hit "cmd+k" in a tab and clear all of the blocks in that tab. If you do that in all of your tabs and it doesn't drastically reduce memory usage, please let me know because that would be very concerning.
+1 on this, my swap is getting obliterated. This is what happens to me almost every time I unlock my mac and left warp open.
Holy moly that's bad. @jomifepe How long was Warp open for, in total, since you launched it? If you haven't restarted it yet, mind grabbing a process sample (from "Sample Process" in the ... menu in the Activity Monitor toolbar) and sharing it with me?
Holy moly that's bad. @jomifepe How long was Warp open for, in total, since you launched it? If you haven't restarted it yet, mind grabbing a process sample (from "Sample Process" in the ... menu in the Activity Monitor toolbar) and sharing it with me?
It has been open for about two days, but I often shut down the mac at the end of the day.
This is something that happens for about 15 seconds after waking the mac from sleep, warp freezes, as it spikes very high in memory usage and it then comes down to the normal.
Here's a Sample Process when it was "normal" (about 1.5GB). I'm not able to get it to spike really high right now, but I'm gonna try to get it once it happens.
Gotcha. Well, today's release (now live via autoupdate) makes some changes relating to memory usage which might fix this for you; give it a shot and let me know if it's any better.
Here are some more Sample Processes from memory spikes that I got:
Yep, that's about where I expected the issue to be. (We're spending a lot of time handling changes to the window size, which appears to happen on unlock.) I'll be starting on memory usage and resizing performance in earnest next week; might take a little while to make the necessary changes (rewriting some core data structures), but should improve things substantially.
Yep, that's about where I expected the issue to be. (We're spending a lot of time handling changes to the window size, which appears to happen on unlock.) I'll be starting on memory usage and resizing performance in earnest next week; might take a little while to make the necessary changes (rewriting some core data structures), but should improve things substantially.
That's great to hear, looking forward to those changes 🚀
I am facing the same issue. I've 5 open tabs and it is taking 2GB.
although clearing the terminal logs using cmd + K drastically brought down the memory usage to 842mb.
to have more insight which tabs use many memory it would be nice to have a tab manager ( Tab Manager #2881)
+1. even with 3 to 4 tabs goign for 2GB RAM, I have switched back to iterm for time being until this gets fixed.
any update here? 😅 cmd+k may work but ideally i wouldn't have to worry about this. This is 2 windows, total of 5 tabs
@brockelmore Whoa! How long had it been since you last restarted Warp?
A few days - notably after running CLI app that produces a lot of text output many times fwiw
Reporting similar issues with 700mb+ RAM usage. I was wondering why my laptop was freezing and turns out Warp was gobbling memory
+1 - Just spent some time hunting down what was slowing my machine and it lead me here.
2GB of memory for 1 window / 2 tabs monitoring local logs during development.
Hey all, thanks for the reports. David (@vorporeal) had to divert his attention to a couple other issues but your feedback is heard -- we're actively investigating ways to address this issue.
I have 6 tabs open with about 2 panes each, I just cleared them all with CMD+K but still getting high memory usage
pls my ram can't take it anymore 😭
It seems to scale with how much text is present in the terminal. Closing & reopening tabs will free a good amount, but it quickly climbs up after continued use.
It's not as drastic, although Warp is usually the biggest contender for memory on my laptop too:
If I close all my tabs, about 6 open, it goes down to 150MB.
From discord user #rustyballz
Hello, I wonder if others have been having issues with Warp's performance... Pretty much weekly I am getting the following scenario you see in the screenshot. When I try to move the warp window or resize it even the smallest amount it will freeze for long periods of time, sometimes when it freezes it will shrink to this size shown and hide off screen, the only way to bring it back is to show all windows and drag it to a position I can see it. Also shown in this screenshot is the incredibly high RAM usage! My development flow has not changed since switching from iTerm2 and I never had these issues in that app even though I also had unlimited scrollback turned on.
Also here after using Warp for a few months now and liking all of the great features, but still getting big consumption of RAM on my system. Right at the moment I'm getting 2GB of memory for two open tabs which is making it really a hard time keeping using the tool and I'm ending up closing it every now and then during my work day.
I am also finding it difficult to use Warp because it can't seem to handle a lot of content in the shell, which happens over time.
+1 on this issue, been experiencing some terrible memory drain with warp. CMD+K helped the situation but would be nice for a more efficient app out of the box, love it a little too much to replace it :(
