Chris Meyer <cmeyer1...@gmail.com> added the comment:
Here is another way to reproduce this (or an extremely similar) error without a
loop. Since may be a race condition, I'm not sure this works 100% of the time
on all machines - but it did on several machines I tried.
```
import asyncio
loop = asyncio.get_event_loop()
def func():
pass
f = loop.run_in_executor(None, func)
loop.stop()
loop.run_forever()
loop.stop()
loop.run_forever()
loop.stop()
loop.run_forever()
```
```
Error on reading from the event loop self pipe
loop: <ProactorEventLoop running=True closed=False debug=False>
Traceback (most recent call last):
File "C:\Miniconda3\envs\py38\lib\asyncio\windows_events.py", line 453, in
finish_recv
return ov.getresult()
OSError: [WinError 995] The I/O operation has been aborted because of either a
thread exit or an application request
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "C:\Miniconda3\envs\py38\lib\asyncio\proactor_events.py", line 768, in
_loop_self_reading
f.result() # may raise
File "C:\Miniconda3\envs\py38\lib\asyncio\windows_events.py", line 808, in
_poll
value = callback(transferred, key, ov)
File "C:\Miniconda3\envs\py38\lib\asyncio\windows_events.py", line 457, in
finish_recv
raise ConnectionResetError(*exc.args)
ConnectionResetError: [WinError 995] The I/O operation has been aborted because
of either a thread exit or an application request
```
----------
_______________________________________
Python tracker <rep...@bugs.python.org>
<https://bugs.python.org/issue39010>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
