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

[1.7] Possible slow memory leak #24

Closed
DarkGuardsman opened this issue May 30, 2018 · 1 comment
Closed

[1.7] Possible slow memory leak #24

DarkGuardsman opened this issue May 30, 2018 · 1 comment
Labels
bug Medium priority Can wait but not forever

Comments

@DarkGuardsman
Copy link
Member

Unable to tell if this is a bug with AS or one of the testing mods. However, there is a slow crawl of memory usage going from 500mb to 1000mb. This will cycle very minute roughly before GC clears up the ram.

Likely sources are the packet or particle system. As both generate a lot of objects that could be filling up the memory.

Solutions: Create another object pool to store dead objects for reuse. As well to stop sending 100s of packets to the client every tick. This can be done by sending the raw data and caching it client side.

@DarkGuardsman DarkGuardsman added bug Medium priority Can wait but not forever labels May 30, 2018
@DarkGuardsman
Copy link
Member Author

After doing a bit of testing this might just be Minecraft itself. Still very odd, without any mods it spikes up between 300mb & 500mb every few seconds. I think more testing is needed to see if a possible patch could be made.

New theory: AI and collision code.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Medium priority Can wait but not forever
Projects
None yet
Development

No branches or pull requests

1 participant