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

Memory Leak - Playing new levels slowly eats up RAM #2

Closed
Tatwi opened this issue Aug 18, 2018 · 1 comment
Closed

Memory Leak - Playing new levels slowly eats up RAM #2

Tatwi opened this issue Aug 18, 2018 · 1 comment

Comments

@Tatwi
Copy link
Owner

Tatwi commented Aug 18, 2018

Each time a level is generated and destroyed, some RAM is not released. I don't know where this issue might be coming from at this time.

@Tatwi
Copy link
Owner Author

Tatwi commented Nov 17, 2020

Resolved by removing SlickUI in commits:
390b78c
f6f05c1

The problem was that none of the objects created by SlickUI were ever removed from RAM, even when explicitly told to remove specific each object individually. This lead to gigabytes worth of memory usage in a matter of a few seconds of starting and exiting levels.

Using the Win64 build of NWjs, the game's memory usage now hovers between 252-300MB, which is pretty much the same as Microsoft Edge and Google Chrome at the New Tab screen.

Side Note: Removing SlickUI also solved the poor performance problems I noticed on the Intel Core2 Quad Q8200 / AMD R9 270 based desktop that my kids use as well as my Intel Celeron N3450 based laptop (both running Win10 64Bit).

@Tatwi Tatwi closed this as completed Nov 17, 2020
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

1 participant