[pywin32-bugs] [ pywin32-Bugs-1605282 ] WaitForSingleObject doesn't release GIL?
OLD project page for the Python extensions for Windows
Brought to you by:
mhammond
From: SourceForge.net <no...@so...> - 2006-11-29 22:44:29
|
Bugs item #1605282, was opened at 2006-11-30 01:23 Message generated for change (Comment added) made by mhammond You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=1605282&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: Closed >Resolution: Invalid Priority: 5 Private: No Submitted By: Sturla (sturlamolden) Assigned to: Nobody/Anonymous (nobody) Summary: WaitForSingleObject doesn't release GIL? Initial Comment: >From the looks of the SWIG interface win32event.i, WaitForSingleObject, WaitForSingleObjectEx and WaitForInputIdle doesn't release the GIL. Sturla Molden ---------------------------------------------------------------------- >Comment By: Mark Hammond (mhammond) Date: 2006-11-30 09:44 Message: Logged In: YES user_id=14198 Originator: NO The GIL is never manipulated directly in the .i file. Check out the generated code in win32eventmodule_win32.cpp and you will see the GIL *is* release for these functions.... static PyObject *_wrap_WaitForInputIdle(PyObject *self, PyObject *args) { ... Py_BEGIN_ALLOW_THREADS _result = (DWORD_WAITAPI )WaitForInputIdle(_arg0,_arg1); Py_END_ALLOW_THREADS ---------------------------------------------------------------------- Comment By: Sturla (sturlamolden) Date: 2006-11-30 04:15 Message: Logged In: YES user_id=1511707 Originator: YES And since these wait functions holds the GIL while they wait, we (may) get a deadlock. ---------------------------------------------------------------------- Comment By: Sturla (sturlamolden) Date: 2006-11-30 04:10 Message: Logged In: YES user_id=1511707 Originator: YES And since these wait functions holds the GIL while they wait, we (may) get a deadlock. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=1605282&group_id=78018 |