Michael Goldish added the comment:
OK, I caught the crash with a debug build of Python 3.4.3.
I have a core dump and even the process itself still alive in memory. I can
provide any information you need. I can also explain how to debug a core dump
with Visual Studio, if necessary.
This time
Michael Goldish added the comment:
Sorry, you're wrong: the proactor event loop heavily uses the _overlapped
module which is implemented in C. A crash in the garbage collector is more
likely a bug in asyncio/your application, than a bug in Python itself.
I'm aware of that. I assumed
Michael Goldish added the comment:
I'm not sure where to post this as the issue is closed:
I've encountered the same problem. I don't have a stack trace to share at the
moment but I know it's almost (or entirely) identical.
My context:
- Windows
- Happens with Python 3.4.2 and 3.4.3
Michael Goldish added the comment:
I caught another crash just now, this time in update_refs(). A stack trace is
attached below. I still think this is the same issue.
static void
update_refs(PyGC_Head *containers)
{
PyGC_Head *gc = containers-gc.gc_next;
67382D60 mov rdx
Michael Goldish added the comment:
I don't see a reason to assume the machine was running out of memory. After
each crash the process was kept alive by one of those Windows crash dialogs -
the process terminated unexpectedly or similar. I could see exactly how much
memory was occupied
Michael Goldish added the comment:
Why do you consider that it's the same issue?
Because it's a very similar stack trace, the crash itself is in
subtype_dealloc(), it happens once every few days, asyncio is involved, and the
issue is relatively new - I couldn't find another bug report
Michael Goldish added the comment:
That's nearly 4 GB. I somehow doubt your app is actually trying to allocate
that much memory
There's no reason for the app to allocate that much memory in a single call.
It's using almost 4 GB of memory in total today, but that makes sense given its
load
Michael Goldish added the comment:
It looks like you are running your app on Windows. Are you using the proactor
event loop?
Yes.
In Python 3.4.3, I fixed a *lot* of crashes and race conditions in the
proactor event loop. There are maybe more race conditions.
I've already tried Python
