[Swig-devel] [ swig-Bugs-1899731 ] SWIG 1.3.33 does not support multiple Python interpreters

[SourceForge.net <no...@so...>]

Bugs item #1899731, was opened at 2008-02-22 11:35
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=101645&aid=1899731&group_id=1645

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: python
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: rather_not_disclose (xxxyyyzzz)
Assigned to: Nobody/Anonymous (nobody)
Summary: SWIG 1.3.33 does not support multiple Python interpreters

Initial Comment:
As discussed on the mailing list: SWIG does not generate modules compatible with multiple python interpreters.

Bug #1: Infinite loop in the initialization function

Bug #2: There was some issue with the delete function

Bug #3: Each swig module loaded per interpreter leaks memory (horribly if your module is big)


Bug #4: If you start two interpreters and import swig modules in each (simultaneously), after ending the first interpreter, the second interpreter sometimes has cleaned up all of its swig objects, with tragic results 

(Start 1
import swiga
(Start 2
import swiga
PyEndInterpreter 1,
interpreter2's swiga may be corrupted.


Bug #4: The static objects created in the object_swigregister functions are shared between interpreters, which allows them to get deleted by one interpreter and have that cross over into the other interpreter. 

etc.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=101645&aid=1899731&group_id=1645