[issue11693] memory leak in email.generator.Generator().flatten() method

Terry J. Reedy added the comment: >From Anaury's report, this is fixed in 2.7. Email in current 3.x has been >re-written. -- nosy: +terry.reedy resolution: -> fixed stage: -> resolved status: open -> closed ___ Python tracker

[issue11693] memory leak in email.generator.Generator().flatten() method

Kaushik Kannan added the comment: I'm on Ubuntu 10.04 with Python 2.6.5, Python 3.1 is also available in the repos, I'll try that and post back. -- ___ Python tracker ___ _

[issue11693] memory leak in email.generator.Generator().flatten() method

Amaury Forgeot d'Arc added the comment: I replaced guppy by a debug build of Python and a simple "print sys.gettotalrefcount()". Indeed, I see a reference leak with Python2.6 (10 more references on every loop). There seems to be no leak with Python2.7. Which version of Python do you use?

[issue11693] memory leak in email.generator.Generator().flatten() method

Kaushik Kannan added the comment: The memory usage trace as printed out by guppy is attached. For every new call of the Generator.flatten() method by the MIMEMultipart.as_string() method, the number of objects increases by 3 and the total size increases by 484Bytes. -- Added file: htt

[issue11693] memory leak in email.generator.Generator().flatten() method

New submission from Kaushik Kannan : I wrote a daemon to monitor a directory and send out emails periodically. To create the email, I used MIMEMultipart() object. When as_string() method is called on the MIMEMultipart() object, it seemed to cause memory leaks. On looking at the as_string() met

[issue11693] memory leak in email.generator.Generator().flatten() method

Changes by Kaushik Kannan : -- components: IO, Library (Lib) files: debug_as_string.py nosy: Kaushik.Kannan, barry, r.david.murray priority: normal severity: normal status: open title: memory leak in email.generator.Generator().flatten() method type: resource usage versions: Python 2.6 A