[ODE] Allocation problem?
jk at spiderland.org
Wed Jun 7 10:02:11 MST 2006
On Jun 7, 2006, at 12:28 PM, Jon Watte (ODE) wrote:
> This already got implemented once AFAICR. There was a big
> discussion WRT
> the overhead of malloc() vs the overhead of a linear allocator vs
> whether there should be one big block or on-demand allocated small
> blocks, vs static block re-use, ...
> Thinking about it: did that ever actually make it into the
> codebase? If
> it did, then the dALLOC failing could be because of some heap
> corruption, instead of running out of stack.
I believe this issue has been coming up over and over again, literally
for a couple of years, and I believe a fix is still not in the code
I've been using a modified version of the patch outlined here:
My modification is shown here (in the quoted text):
Personally, I feel that fixing this is extremely important. Using
alloca, even with an increased stack size, adding objects into a
simulation will eventually cause ODE to crash. Though this may work
fine for applications in which the user knows ahead of time how many
objects can be created, it's really not acceptable for an application
which allows runtime creation of arbitrary objects (which is what I
used ODE for -- http://www.spiderland.org/breve ).
- jon klein
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the ODE