Multiple interpreters retaining huge amounts of memory

[Bronner, Gregory]

What objects need to be shared across interpreters?

My thought was to add an interpreter number to the PyThreadState structure, to increment it when Py_NewInterpreter is called, and to keep track of the interpreter that creates each object. On deletion, all memory belonging to these objects would be freed.

Thoughts?

-----Original Message-----
From: "Martin v. Löwis" [mailto:martin at v.loewis.de] 
Sent: Friday, February 01, 2008 8:34 PM
To: python-list at python.org
Subject: Re: Multiple interpreters retaining huge amounts of memory

> Is there some way to track references per interpreter, or to get the 
> memory allocator to set up seperate arenas per interpreter so that it 
> can remove all allocated memory when the interpreter exits?

No. The multi-interpreter feature doesn't really work, so you are basically on your own. If you find out what the problem is, please submit patches to bugs.python.org.

In any case, the strategy you propose (with multiple arenas) would *not* work, since some objects have to be shared across interpreters.

Regards,
Martin

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

This message is intended only for the personal and confidential use of the designated recipient(s) named above.  If you are not the intended recipient of this message you are hereby notified that any review, dissemination, distribution or copying of this message is strictly prohibited.  This communication is for information purposes only and should not be regarded as an offer to sell or as a solicitation of an offer to buy any financial product, an official confirmation of any transaction, or as an official statement of Lehman Brothers.  Email transmission cannot be guaranteed to be secure or error-free.  Therefore, we do not represent that this information is complete or accurate and it should not be relied upon as such.  All information is subject to change without notice.

--------
IRS Circular 230 Disclosure:
Please be advised that any discussion of U.S. tax matters contained within this communication (including any attachments) is not intended or written to be used and cannot be used for the purpose of (i) avoiding U.S. tax related penalties or (ii) promoting, marketing or recommending to another party any transaction or matter addressed herein.