Re: [Pyode-user] bug: read from free'd memory when joint in jointgroup

[Chris B. <chr...@gm...>]

On 16/08/06, Matthias Baas <ba...@ir...> wrote:
> Now the situation you describe above (i.e. dWorldDestroy() is called
> before the Python joints are deallocated) shouldn't occur because the
> Python joints keep a reference to the World object they are in. I did
> this so that the World object is deallocated after the joints. But I'm
> not sure if Python really cares about the reference counts when the
> interpreter is actually shut down.

I think the key thing here is that I'm using garbage collection module
gc which doesn't enforce any ordering on the destruction of objects. I
just disabled it in one of my test cases and it no longer crashes.