[ODE] why ode crash my app?

Mark Williams mark at image-engine.com
Fri Apr 20 10:03:12 MST 2007

so with body) and few trimesh
>> (only geoms for collision). How have you correct your crashes?
> 600 is a lot of boxes and definitely sounds like a quantity that I
> would expect to cause a stack overflow - regardless of step function.

I've successfully simulated ~30,000 trimesh objects using default stack 
size on Linux, and QuadTree space.

> 2 - use the 'dUSE_MALLOC_FOR_ALLOCA' build option in include/config.h

Unfortunately this can cause ODE to leak serious amounts of memory, and 
some alloca() calls don't go through the dALLOCA macro - the big one in 
HashSpace is a good example of this.


More information about the ODE mailing list