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

Possible memory leak #23

Open
zivoy opened this issue Jul 17, 2019 · 1 comment
Open

Possible memory leak #23

zivoy opened this issue Jul 17, 2019 · 1 comment

Comments

@zivoy
Copy link

zivoy commented Jul 17, 2019

I am running the bot on a GCP instance that has only 600mbs of ram.
The bot works for the most part and most things render fine but problems occur when rendering long death streams, the bot uses up all the ram and takes a long time to render.
this doesn't happen when rendering normal things like jumps or a regular streams and sliders.

--ziv

@LeaPhant
Copy link
Owner

Rendering beatmaps just requires a lot of memory. Beatmap Objects can use 100 MB of memory for maps with a lot of objects and that's for every render thread (one per cpu thread) cause I don't think I can share it. I don't know how I can improve this in the future cause Node.js has limited control in this regard and I'm also not well-versed in this kind of optimization.

If you have a specific map where you think there could be a memory leak send it to me, cause I've tested some and memory usage scales with the amount of hit objects.

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