From: Chris B. <chr...@gm...> - 2007-06-18 23:12:20
|
On 18/06/07, Chris Spencer <chr...@gm...> wrote: > On 6/18/07, Jon Watte (ODE) <hpl...@mi...> wrote: > > ODE is not thread safe. You can only manipulate objects when you know > > that the world collision/simulation isn't running. > > ODE does not have any known bugs in memory management. > > The bug I'm referring to is the one reported at > https://sourceforge.net/tracker/?func=detail&atid=382799&aid=1566350&group_id=24884 > > Even for thread-safe code, ODE tends to crash quite regularly when I > try to add or remove large numbers of bodies/geoms from a simulation. One common problem with large number of bodies is running out of stack space. You can increase the stack space available to your program by running 'ulimit -s unlimited' from your shell, before you start your ODE program. But if you run python under gdb or similar you'll be able to see exactly which function is crashing (the stack problem is dSolveLCP). |