Message261473
I understand that asyncio is not .NET and did my best to implement "by the book" according to the asyncio documentation I read extensively.
My await_async function has in fact nothing in common with what I would do in .NET but is hopefully as close as possible to the canonical way to create and consume a loop.
The only maybe non standard thing I do is create a lot of short-lived loops, but nothing in the documentation indicates this heavy usage can cause instability/freezing.
The case I am reporting can therefore be seen as an asyncio stress test and is worrisome as if there is indeed a bug, it could occur randomly when creating a single loop as well.
So far, I cannot see anything in my implementation that would be fundamentally wrong (for example: do we need to always call close() on a loop, or is it taken care of by the GC). I can provide remote access to my screen when the issue occurs if it helps, and will post a bounty on my StackOverflow question tomorrow. |
|
Date |
User |
Action |
Args |
2016-03-09 20:28:47 | Erwin Mayer | set | recipients:
+ Erwin Mayer, gvanrossum, vstinner, yselivanov |
2016-03-09 20:28:47 | Erwin Mayer | set | messageid: <1457555327.78.0.158085906825.issue26520@psf.upfronthosting.co.za> |
2016-03-09 20:28:47 | Erwin Mayer | link | issue26520 messages |
2016-03-09 20:28:47 | Erwin Mayer | create | |
|