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 #25

Open
PerryRylance opened this issue Dec 13, 2020 · 2 comments
Open

Memory leak #25

PerryRylance opened this issue Dec 13, 2020 · 2 comments
Labels
bug Something isn't working

Comments

@PerryRylance
Copy link
Owner

PerryRylance commented Dec 13, 2020

The AI quickly creates an apparent memory leak when running fine grained predictions.

I believe this is box2d.js.

Please see here kripken/box2d.js#114

Leak fixed, unrelated to Box2D version, see below

@PerryRylance PerryRylance added the bug Something isn't working label Dec 13, 2020
@PerryRylance
Copy link
Owner Author

Entity::applyGravity is leaking, need to destroy the local vectors explicitly

@PerryRylance
Copy link
Owner Author

This has been partly solved in #26 , however anywhere b2Vec2 in particular is instantiated, they must be explicitly destroyed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant