Message389969
OK: further.
Two options are suggested:
There are different options to solve this issue:
* Reset _tstate_lock before using it... not sure that it's worth it, since we are going to delete the threading.Thread object with its _tstate_lock object anymore. After calling fork, the child process has exactly 1 thread: all other threads have been removed.
* Modify release_sentinel() to not use the lock: avoid PyThread_release_lock() call.
** as to option 1 - it is 'worth it' if it stops the crashes
** This is deeper than I usually go in Python code - but I'll make an effort - help is appreciated. |
|
Date |
User |
Action |
Args |
2021-04-01 09:59:19 | Michael.Felt | set | recipients:
+ Michael.Felt, vstinner, shihai1991 |
2021-04-01 09:59:19 | Michael.Felt | set | messageid: <1617271159.96.0.448458221003.issue40092@roundup.psfhosted.org> |
2021-04-01 09:59:19 | Michael.Felt | link | issue40092 messages |
2021-04-01 09:59:19 | Michael.Felt | create | |
|