-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Huge Memory Leak #109
Comments
Yeah, I'm aware of this from this post and it seems like I'll have to profile the whole code to see where all the memory is being used. Your |
Yep |
Mine works fine ig |
The Workloads are not getting released correctly In other words if the client seek the video 4 times it gets handled by 4 clients and create session and cache for each of those files in media session of each clients hence increasing the ram consumption |
ho we can solve this problem? |
I have used daemon service and timer to auto stop and start again every 3 hour? does it work? |
I'm working on a fix. I'll update it soon |
In a 64GB Dedicated Server i ran The Bot For 7h with 4 clients
After 2 hours uptime the memory usage was about 5GB with a total of 400 workload (sum of all workloads of bot in approx)
After 7 hours of uptime the memory usage was a whopping 16GB with just total load of less than 70
So we can say that the memory is not getting released even a bit even when load became 1/5th of the initial load
I whould really like to see an end to this 🥲, idk if the FileStream code or if the pyrogram itself is leaking memory but either way it's clear that there is a memory leak and i think it's from the media_sessions cuz the size of media_sesssion had also respectively without going down again
if u need any more info or want to test any patches I'll be there for u xd
The text was updated successfully, but these errors were encountered: