A possible bug in python threading/time module?
vm_usenet at yahoo.com
Wed Jul 2 10:39:40 CEST 2003
I've been running this segment of code (slightly simplified to
emphasize the main part):
----START of Script----
sem = threading.Semaphore(2048)
j = 0
for i in range(1000):
j = j+1
for i in range(4096):
----END of Script----
I ran it on python 2.2.2 and python 2.3b1, and on both all of the
threads started successfully, acquiring the semaphore until 0
resources were left.
However, about 10-20 threads remain active after a while (and the
semaphore is lacking resources, respectively). I waited for about two
hours, and nothing changed - it appears to be hanging. Did anyone
encounter this behaviour before?
Am I the only one who ran into this situation? Is this a bug?
Thanx in advance
More information about the Python-list