nail down memory management, and object lifetime, add reference counting when necessary

macbury / bullet

Automatically exported from code.google.com/p/bullet

0 stars 0 forks source link

nail down memory management, and object lifetime, add reference counting when necessary #13

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago

CollisionShape can be re-used, so reference counting makes sense there.

Also, allowing custom memory allocator is very useful, instead of global system 
new/delete

Original issue reported on code.google.com by erwin.coumans on 26 Sep 2006 at 4:53

GoogleCodeExporter commented 9 years ago

All memory allocations inside Bullet core (Bullet/src folder) are routed 
through 
btAlignedAllocator. It is up to the user to allocate/deallocate memory for 
collision 
shapes. 

Bullet keeps the memory strategy very simple: the one who allocates memory is 
responsible for freeing it.

Original comment by erwin.coumans on 11 Feb 2008 at 6:33

Changed state: Started

GoogleCodeExporter commented 9 years ago

All memory allocations in Bullet should be leak-free now. 

We need to keep checking before each release that the demos cleanup memory, to 
show 
good practice.

Original comment by erwin.coumans on 31 Mar 2008 at 4:20

Changed state: Fixed