[issue38680] PyGILState_Release does not release gil correctly, resulting in deadlock

2019-11-05 Thread Damien LEFEVRE
Damien LEFEVRE added the comment: I see the same problem. We call python functions from C++ and use this locking class within each call: ''' #pragma once #ifdef _DEBUG #undef _DEBUG #include #define _DEBUG #else #include #endif // _DEBUG #includ

[issue38680] PyGILState_Release does not release gil correctly, resulting in deadlock

2019-11-05 Thread Damien LEFEVRE
Damien LEFEVRE added the comment: @ronaldoussoren The issue here is that the behavior between Python 3.6 and 3.7 has changed. Our code runs perfectly fine with 3.6. We release the lock each time our functions get out of scope and so we know for sure there is no lock left behind. Starting

[issue38680] PyGILState_Release does not release gil correctly, resulting in deadlock

2019-11-19 Thread Damien LEFEVRE
Damien LEFEVRE added the comment: Back to testing this. I have the same issue on Linux, i.e: the deadlock on PyGILState_Ensure. I cannot test 3.8 because many of the modules are not yet available for this version. I'll try making a small test application to reproduce the

[issue38680] PyGILState_Release does not release gil correctly, resulting in deadlock

2019-11-21 Thread Damien LEFEVRE
Damien LEFEVRE added the comment: Here is a code example reproducing the issue. -- Added file: https://bugs.python.org/file48728/interpreterlock.zip ___ Python tracker <https://bugs.python.org/issue38