-
Notifications
You must be signed in to change notification settings - Fork 6
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
bug: Memory leak #55
Comments
it seems to be related to some caching issue, i have done some profiling and memory only goes up when we send a new command, for instance if i do !tuturu, mem goes up but if i do it again, mem does not goes up also if we use commands that do not use external website like access, who etc, memory does not goes up
|
#69 Fixed the majority of this issue. A small leak still present but it's nothing compared to previous leak. |
yeah i think its because yts is not working also, btw i have set a memory limit in pterodactyl so if it goes over the limit, the container will restart |
Build in use: 55655cc
![image](https://private-user-images.githubusercontent.com/11679883/328113330-d2cf6af5-244e-4f0d-bcc3-6090545d7415.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MzkyNzgxNjgsIm5iZiI6MTczOTI3Nzg2OCwicGF0aCI6Ii8xMTY3OTg4My8zMjgxMTMzMzAtZDJjZjZhZjUtMjQ0ZS00ZjBkLWJjYzMtNjA5MDU0NWQ3NDE1LnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNTAyMTElMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjUwMjExVDEyNDQyOFomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTQ0MzIzZjcwNGNjMTE5N2VmMmY5MDFkYjUzYTY4MjQ1Nzk4ZTNjMDdiNDhjNmU0MjM2OTVkNmQ5ZjRiMzU2ZDMmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.bgsRzjYdj9j1Q3KkHDVHIIbjJdw9JR37b9f12fHJGyM)
Depending the usage from clients, torchlight lead to a memory leak happens earlier.
Already the second time it occurs. First time was after 37d of uptime, second time was after 23 days.
The text was updated successfully, but these errors were encountered: