#2.1Gb of RAM consumption

9 messages · Page 1 of 1 (latest)

merry hawk
#

I am wondering why the wrap proccess is wasting so much RAM

image.png
final fableBOT
#

Hi @merry hawk. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:

#

There have been several reports of high memory usage by Warp, as seen in the issues reported on GitHub. Some users have reported memory usage growing up to 24GB, 2.4GB with 10 tabs, and even peaking at 150GB in some instances. This issue seems to occur over time, with memory usage starting at a reasonable level and then growing as the application is used.

The exact cause of this high memory usage is not explicitly stated in the provided sources. However, some users have speculated that it could be due to a memory leak, as the memory usage seems to increase over time and does not decrease even when tasks are completed. There are also suggestions that the issue could be related to the handling of multiple tabs and panes in Warp, or possibly the "Warpify" subshell feature.

The Warp team is aware of these issues and has been actively investigating ways to address them. However, as of the latest updates in the provided sources, no specific solutions or workarounds have been provided.

For more details, you can refer to the following GitHub issues:

Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:

#

@merry hawk kapa.ai is still learning and improving, please let us know how it did by reacting below

merry hawk
#

help

wooden terrace
#

I don't think Kapa has the ability to read the text inside the image

#

As Kapa stated, the dev team is aware of this and are working on it... You can find some more info at the links provided above... but as a potential temporary solution, if you tend to leave the app open all day/every day... once in awhile while working, just fully shut down the app, wait at least a few seconds or more for the memory to free up, than re-open it...

For me personally, I've only had this issue happen once and it was after I left Warp running for 3 days while I was out of town because I forgot to close it... after I restarted it I haven't had the problem

merry hawk
#

Ok, thanks