Chipmunk Physics

I've found that calling cpSpaceAddPostStepCallback consumes memory that seems to be never released, even on cpSpaceFree.

For example, in ChipmunkDemo:
Task Manager shows that at LogoSmash it uses ~8600Kb. After switching to Sensors(which uses PostStep callbacks) and waiting about 10 minutes, you'll notice that program uses much more memory. Back to LogoSmash - it is ~31000Kb instead of ~8600Kb.

So, 21 Mb of memory in 10 minutes - is this a bug or am I missing something?

Confirmed. That's kind of a nasty one too. I was forgetting to free a hash set that got allocated each frame a post step callback was used.

Good catch. I usually check the demo app for memory leaks before releasing, but I guess I missed that one.

How do I fix this? It eats up my memory since I need to call it constantly.

This bug has been fixed in trunk, but it looks like it hasn't made it out into a release yet.

Thanks for the information and the fixing

Will use the trunk until the release comes out.

Just ran into the leak myself. Thanks for the fix!

Keep up the awesome work!

So I think this leak may have existed since I implemented the post-step callback feature... Not sure how it went so long without being noticed.