[pywin32-bugs] [ pywin32-Bugs-3612200 ] Crash in Python COM Server is Python was shutdown

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

Bugs item #3612200, was opened at 2013-04-29 07:41
Message generated for change (Comment added) made by mhammond
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=551954&aid=3612200&group_id=78018

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: None
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Stefan Schukat (sschukat)
Assigned to: Nobody/Anonymous (nobody)
Summary: Crash in Python COM Server is Python was shutdown

Initial Comment:
If a Python implemented COM object is referenced by a client longer than lifetime of the Python runtime the hosting process crashes if during the release of the COM object Python functions are accessed. This is fixed by a check if Python is still initialized in the process.

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

>Comment By: Mark Hammond (mhammond)
Date: 2013-04-29 23:34

Message:
Can you give some details on how Python can become uninitialized at this
time?  pywin32 never finalizes Python, and I expect that if it was
finalized while COM objects were alive we would have far more problems than
just this one (eg, if rather than the object being destructed it instead
attempt to make a "normal" call things would go pear-shaped pretty quickly
I'd expect)

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

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=551954&aid=3612200&group_id=78018