This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author michaelg
Recipients gvanrossum, karamanolev, michaelg, r-englund, vstinner, yselivanov
Date 2015-03-14.12:25:36
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1426335936.27.0.872959744847.issue23187@psf.upfronthosting.co.za>
In-reply-to
Content
> 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.
History
Date User Action Args
2015-03-14 12:25:36michaelgsetrecipients: + michaelg, gvanrossum, vstinner, yselivanov, karamanolev, r-englund
2015-03-14 12:25:36michaelgsetmessageid: <1426335936.27.0.872959744847.issue23187@psf.upfronthosting.co.za>
2015-03-14 12:25:36michaelglinkissue23187 messages
2015-03-14 12:25:36michaelgcreate