[New-bugs-announce] [issue23846] asyncio : ProactorEventLoop raised BlockingIOError when ThreadPoolExecutor has many workers
report at bugs.python.org
Thu Apr 2 06:00:18 CEST 2015
New submission from SeungHyun.Hwang:
I tested on python3.4.2, windows 7
1. Only proactorEvent issued.
2. ThreadPoolExecutor has many workers (in the attached example file, worker count 20,000)
3. The loop does run_in_executor more call than worker count (in the attached example file, 40,000 calls)
4. After some random seconds, raise BlockingIOError
BlockingIOError: [WinError 10035] A non-blocking socket operation could not be completed immediately.
exception calling callback for <Future at 0x1ab89ef0 state=finished returned NoneType>
Traceback (most recent call last):
File "c:\Python342\Lib\concurrent\futures\_base.py", line 297, in _invoke_callbacks
File "c:\Python342\Lib\asyncio\futures.py", line 410, in <lambda>
File "c:\Python342\Lib\asyncio\base_events.py", line 403, in call_soon_threadsafe
File "c:\Python342\Lib\asyncio\proactor_events.py", line 449, in _write_to_self
I guess that proactor's _write_to_self method misses exception handle.
# This may be called from a different thread, possibly after
# _close_self_pipe() has been called or even while it is
# running. Guard for self._csock being None or closed. When
# a socket is closed, send() raises OSError (with errno set to
# EBADF, but let's not rely on the exact error code).
csock = self._csock
if csock is not None:
logger.debug("Fail to write a null byte into the "
Ps: It's my first publication. Hope you understand my poor comment..
nosy: gvanrossum, haypo, kernel0, yselivanov
title: asyncio : ProactorEventLoop raised BlockingIOError when ThreadPoolExecutor has many workers
versions: Python 3.4
Added file: http://bugs.python.org/file38801/example_thread_executor.py
Python tracker <report at bugs.python.org>
More information about the New-bugs-announce