➜
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 2007-10-20 06:11 by andres, last changed 2022-04-11 14:56 by admin. This issue is now closed.
| Files | ||||
|---|---|---|---|---|
| File name | Uploaded | Description | Edit | |
| sockettest.py | andres, 2007-10-20 06:11 | |||
| Messages (3) | |||
|---|---|---|---|
| msg56601 - (view) | Author: andres (andres) | Date: 2007-10-20 06:11 | |
Repeated socket connection attempts hang for >2s on Python 2.5.1 & OS X 10.4 after 250 attempts have been made. |
|||
| msg56651 - (view) | Author: Guido van Rossum (gvanrossum) *  |
Date: 2007-10-22 16:45 | |
Odd. Smells like an OSX issue that we can't do anything about. I note that only attempts 250, 500, 750 (and so on if you increase the counter) have this behavior. I wonder if you'r simply filling up some kernel queue too fast; if I insert time.sleep(0.001) in the for loop it won't happen. |
|||
| msg56657 - (view) | Author: Facundo Batista (facundobatista) * |
Date: 2007-10-22 20:38 | |
What happens if you force the garbage collector to collect the just opened and not used socket? Maybe the problem is that the operating system run out of file handlers (if you leave some time in the middle, the GC collects the sockets, freeinig the file handlers). Other test could be to disable the GC, and see what happens with that time.sleep in the middle. |
|||
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2022-04-11 14:56:27 | admin | set | github: 45646 |
| 2007-10-22 20:38:11 | facundobatista | set | nosy:
+ facundobatista messages: + msg56657 |
| 2007-10-22 16:45:05 | gvanrossum | set | status: open -> closed resolution: wont fix messages: + msg56651 nosy: + gvanrossum |
| 2007-10-20 06:11:09 | andres | create | |