On 10/18/05, David Anderson <david.anderson@calixo.net> wrote:
> * Crashes and deadlocks in the python bindings. This seems to be
> rapidly turning into a can of worms, as mod_python is revealing
> some problems that date back to a long time with our bindings.
>
> Two cases in point. The first, is that calling apr_terminate
> crashes on windows, because it is called using atexit(), ie. at a
> point where the python interpreter has shut down and can no longer
> process callbacks that get invoked. We are working on a fix to
> this, which we'll be getting out for testing shortly.
>
> The second has to do with multithreading. The current code is not
> careful enough with memory management and locking, which crashes
> multithreaded programs calling our bindings. Both ViewCVS and
> Trac, if running over mod_python (one of ViewCVS' 2 operation
> modes, and one of Trac's 3 with FastCGI), are using our bindings in
> a multithreaded fashion, and are at risk.
I've fixed this issue in r16807, r16808, and 16817. I've proposed
these fixes for backport. Marc Haesen has verified that these
revisions fix the issue. So, it looks like our Python bindings are
ready to go!
Cheers,
David
--
David James -- http://www.cs.toronto.edu/~james
Received on Wed Oct 19 16:44:54 2005