➜
This issue tracker has been migrated to GitHub,
and is currently read-only.
For more information,
see the GitHub FAQs in the Python's Developer Guide.
Created on 2018-12-05 12:55 by Hexorg, last changed 2022-04-11 14:59 by admin. This issue is now closed.
| Files | ||||
|---|---|---|---|---|
| File name | Uploaded | Description | Edit | |
| bug_test.py | Hexorg, 2018-12-05 12:55 | |||
| Messages (2) | |||
|---|---|---|---|
| msg331106 - (view) | Author: Stan (Hexorg) | Date: 2018-12-05 12:55 | |
Checking if thread.is_alive() while thread is checking on Process.is_alive() seemingly causes undefined behavior. The attached POC is expected to print "ThreadN.data == 1999" for N in range(0, 20) with some repeats. However the integers are spread all over the place. Moreover sometimes one or more of the threads never terminate resulting in technically infinite amount of "ThreadN.data == ###" prints. In python2.7.15 I never observed a thread lock (only early terminations), but in python3.4.8 I did. You may have to adjust max_count variable to have higher success rate of thread locking. I got about 40% chance of `python3 bug_test.py` never finishing on an Intel(R) Core(TM) i7-4610M CPU @ 3.00GHz |
|||
| msg407601 - (view) | Author: Irit Katriel (iritkatriel) *  |
Date: 2021-12-03 21:02 | |
Use this queue for multithreaded applications: https://docs.python.org/3/library/queue.html Mixing multiprocessing with multithreading often doesn't work. |
|||
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2022-04-11 14:59:08 | admin | set | github: 79600 |
| 2021-12-03 21:02:37 | iritkatriel | set | status: open -> closed nosy: + iritkatriel messages: + msg407601 resolution: not a bug stage: resolved |
| 2018-12-05 12:55:10 | Hexorg | create | |