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

bug: Memory leak #55

Open
Rushaway opened this issue May 6, 2024 · 4 comments
Open

bug: Memory leak #55

Rushaway opened this issue May 6, 2024 · 4 comments

Comments

@Rushaway
Copy link
Member

Rushaway commented May 6, 2024

Build in use: 55655cc
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.
image

@Rushaway
Copy link
Member Author

Rushaway commented Jul 29, 2024

Ended reaching 1.3Go ram usage and froze the container.
image

@maxime1907
Copy link
Member

maxime1907 commented Aug 4, 2024

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

Filename: /home/maxime-leroy/Documents/git/github/srcdslab/torchlight/src/torchlight/Commands.py

Line #    Mem usage    Increment  Occurrences   Line Contents
   345     55.2 MiB      0.6 MiB           3               resp = await asyncio.wait_for(

@Rushaway
Copy link
Member Author

Rushaway commented Aug 17, 2024

#69 Fixed the majority of this issue. A small leak still present but it's nothing compared to previous leak.
image

@maxime1907
Copy link
Member

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants