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 Xavion
Recipients The Compiler, Xavion, ztane
Date 2016-09-17.07:01:52
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1474095712.77.0.409064749439.issue28165@psf.upfronthosting.co.za>
In-reply-to
Content
Okay, I've modified the title to match what I've written below.

I've just run some further tests on this problem.  The attached archive contains code samples and the output generated (both with and without garbage collection).

As you can see, the memory stays constant in the first case.  In the second, the presence of the loop is probably what throws a spanner in the works.  Garbage collection seems to make the outcome slightly worse (in the second case).

The situation isn't as bad as I first reported, but the memory does nonetheless keep increasing in the second case (which it probably shouldn't).
History
Date User Action Args
2016-09-17 07:01:52Xavionsetrecipients: + Xavion, ztane, The Compiler
2016-09-17 07:01:52Xavionsetmessageid: <1474095712.77.0.409064749439.issue28165@psf.upfronthosting.co.za>
2016-09-17 07:01:52Xavionlinkissue28165 messages
2016-09-17 07:01:52Xavioncreate