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 today. > Is there any you can run an unoptimized build? I'll try doing that now. I suppose I should build it myself with Py_DEBUG enabled. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue23187> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
