Memory Leak about box2d.js HOT 3 CLOSED

Found some useful info here:

JavaScript, specifically ECMA-262 Edition 5.1, does not support finalizers or weak references with callbacks. Thus, JavaScript code must explicitly delete any C++ object handles it has received. Otherwise the Emscripten heap will grow indefinitely.

With that in mind, I realized that I was creating new b2Vec2 instances, but never destroying the original one. I'm so used to letting the JavaScript garbage collector do that for me.

So instead of creating a new b2Vec on the last line, I re-used the one that already exists:

velocity.set_x(x);
velocity.set_y(y);
this.body.SetLinearVelocity( velocity, this.body.GetPosition() );

Perfect!

from box2d.js.

But is it possible to delete from Box2D the references we no longer need? because reusing is dangerous, I dont know if the reference I passed to box2D is being used internally so any changes could affect existing objects on the scene.
I guess I could check if the functions use copy, reference or pointer for every call, but maybe there is an easier way to free memory.

from box2d.js.

destroy should free the C++ side of things.

On Thu, Jul 18, 2013 at 6:10 AM, jagenjo [email protected] wrote:

But it is possible to delete the references we no longer need? because
reusing is dangerous, I dont know if the reference I passed to box2D is
being used internally so any changes could affect existing objects on the
scene.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/27#issuecomment-21181935
.

from box2d.js.