-
-
Notifications
You must be signed in to change notification settings - Fork 3.7k
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 Memory Usage Due to Remote Auth Caching in wwebjs_auth File #3222
Comments
This comment was marked as off-topic.
This comment was marked as off-topic.
it happend to me, what coud be the problem? |
Same issue, it takes forever for loading up and for the client get ready. |
any update for this? its happen to me. and when service restart, more client sign out automaticly |
Same issue here, I'm sure there is a way to reduce the memory usage.... |
same issue, causing my VM frozen and not responding |
Facing an issue with whatsapp-web.js on Ubuntu. Initially, the RAM usage is around 40% but after 5 to 7 hours of running with the same sessions (no new sessions added), the RAM usage gradually increases to 100%, causing performance issues. 😔 |
it is now unusable when you use the saved auth. Because when it starts it seems load a massive file and the machine hang. |
I was experiencing the same issue after deployment on Heroku. I add some args in the puppeteer options in the file
|
any update for this? |
+1 here. RAM consumption keeps going up every day. |
Is there an existing issue for this?
Describe the bug
I'm experiencing significant memory usage problems with the remote auth feature in my application. Specifically, the caching of data in the
wweb_auth
file is causing my server to consume a large amount of RAM, around 20GB, which is unsustainable. I have around 70 customers, and the frequent synchronization with MongoDB (every 60 seconds) is not alleviating the memory pressure.Expected Behavior
I would expect the remote auth mechanism to handle authentication data more efficiently, without causing excessive memory usage. Ideally, it should be possible to configure it to use less RAM or to avoid keeping large amounts of data in memory.
Actual Behavior
The
wweb_auth
file caching mechanism is causing the application to consume around 20GB of RAM. This high memory usage is not sustainable and leads to performance issues.Steps to Reproduce the Bug or Issue
Relevant Code
No response
Browser Type
Chromium
WhatsApp Account Type
Standard
Does your WhatsApp account have multidevice enabled?
Yes, I am using Multi Device
Environment
Additional context
No response
The text was updated successfully, but these errors were encountered: