Skip to content
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

High RAM usage #43

Open
alizxamax opened this issue Mar 21, 2024 · 6 comments
Open

High RAM usage #43

alizxamax opened this issue Mar 21, 2024 · 6 comments
Labels
bug Something isn't working

Comments

@alizxamax
Copy link

alizxamax commented Mar 21, 2024

سلام
من از این برنامه رو سرور استفاده میکنم
وقتی که به سرور متصل میشم و برنامه وارپ بدون مشکل کار میکنه
اما زمانی که مصرف زیاد میشه مثلا زمانی که تست سرعت میگیرم مصرف رم به قدری میره بالا که سرور فریز میشه
با دستور زیر هم که مصرف رم رو محدود میکنم تا یه جایی درست کار میکنه اما وفتی یه فایل 200 مگ رو دانلود میکنم ، برنامه بسته میشه
systemd-run -p MemoryMax=124M --user ./warp
من از سرور ubuntu 20.04 استفاده میکنم با 1 GB رم
روی ورژن 22 اوبنتو هم تست کردم اما همین مشکل بود
warp version : v1.0.4-rc2

@markpash markpash added the bug Something isn't working label Mar 21, 2024
@markpash
Copy link
Member

Can you please edit your post to include the version you are using? Thanks.

@markpash markpash reopened this Mar 21, 2024
@markpash
Copy link
Member

@alizxamax can you try the latest version? https://github.com/bepass-org/warp-plus/releases/tag/v1.1.0

@alizxamax
Copy link
Author

I tried. RAM usage has improved , but still after three days warp stops due to high RAM usage
Screenshot-34

@markpash
Copy link
Member

@alizxamax I know it's not a good solution, so please use this as a temporary workaround. Try creating a systemd service and setting the following attributes:

LimitNOFILE = "infinity"
Restart = "always"

@rnetis
Copy link

rnetis commented May 15, 2024

Hey there
i ran some test and the best solution til now that i found was setting crontab for every 10 min that resets the systemd service
i'm still reading the code to find out better solution

@theshdowaura
Copy link

@rnetis @alizxamax I know this issue isn't related to the program itself. It is actually due to the memory garbage collection mechanism in Golang's compilation conditions. You can try recompiling the project and setting the variable GOGC to 5 or 10. Good luck!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

4 participants