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 kaizhu
Recipients amaury.forgeotdarc, ezio.melotti, kaizhu
Date 2011-05-15.08:14:42
SpamBayes Score 4.202036e-07
Marked as misclassified No
Message-id <1305447282.94.0.296695128346.issue12075@psf.upfronthosting.co.za>
In-reply-to
Content
explicit gc.collect() doesn't seem to fix the leak in my application.
my current fix is to not re-instantiate the class attribute (which cost ~7mb) during reload & instead reference one created earlier.

i haven't pinpointed y, but i suspect its a corner case, which would rarely occur in general usage.  my class also inherits from subprocess.Popen, which has a __del__ method, which might interfere w/ collection (although gc.garbage says otherwise ;).

the reason i reload is that the script gets modified frequently, which the auto-build system will detect & reload.
History
Date User Action Args
2011-05-15 08:14:42kaizhusetrecipients: + kaizhu, amaury.forgeotdarc, ezio.melotti
2011-05-15 08:14:42kaizhusetmessageid: <1305447282.94.0.296695128346.issue12075@psf.upfronthosting.co.za>
2011-05-15 08:14:42kaizhulinkissue12075 messages
2011-05-15 08:14:42kaizhucreate