-
Notifications
You must be signed in to change notification settings - Fork 27
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
PlayerSnapshot causing EntityPlayer instance leak #38
Comments
hey, i created a branche "fixplayersnapshot" on my fork (https://github.com/StateMC/ModularWarfare/tree/fixplayersnapshot) |
Yes, you are both right. @gameusefly If your commit is working in server-side/client-side feel free to make a pull request to solve the problem. |
@gameusefly I tested it in a forge only env, and it works well on server but doesn't on client. After i leave the game, clientSideDatas are still there. |
@MrMks i pushed a fix for that, feel free to test it :) |
@gameusefly ok, it works now. |
The EntityPlayer leak is now fixed in the newest version of the stable branche |
I checked the heapdump with memory analyze tool (by Eclipse), and it shows that there is a reference link to the instance of EntityPlayer.
And then i checked the code, it seems that there is no methods to remove out-of-dated instances.
So, i think it must be a memory leak issue.
The text was updated successfully, but these errors were encountered: