#2611: Problem with SVN bindings (SVN 1.3.0, Trac r2771)
-----------------------------+----------------------------------------------
Reporter: Manuzhai | Owner: cboos
Type: defect | Status: new
Priority: high | Milestone: 0.11
Component: version control | Version: devel
Severity: major | Resolution:
Keywords: svn130 |
-----------------------------+----------------------------------------------
Comment (by cboos):
In light of [http://trac.edgewall.org/ticket/3455#comment:6 #3455], it
seems clear that the fix in
attachment:application_pool_race_condition_fix.txt is not working in case
of multiple Python subinterpreters (as this is the case by default with
virtual hosts).
The `svn_swig_py_set_application_pool(self, self)` will be called for each
sub-interpreter and therefore at the C level one pool object coming from
one subinterpreter will be used by all the other subinterpreters. This
probably leads to an invalid GC, which destroys that object prematurely,
and that deletes the "_is_valid" string which triggers the message we're
seeing, see comment:64).
So... the workaround for #3455 should most probably also work here.
It remains to be confirmed if the 1.3.2 bindings generated with SWIG >=
1.3.28 are handling the multiple sub-interpreter scenario correctly.
--
Ticket URL: <http://trac.edgewall.org/ticket/2611#comment:67>
The Trac Project <http://trac.edgewall.com/>
_______________________________________________
Trac-Tickets mailing list
[email protected]
http://lists.edgewall.com/mailman/listinfo/trac-tickets
