Urgent : How to do memory leaks detection in python ?

[Bronner, Gregory]

This is not entirely true:
Symptoms of increasing memory usage are either because
 
a) you are keeping too much data around in user accessable memory
(likely)
b) you are creating self-referential structures that are not garbage
collected (also likely)
c) You have memory leaks in underlying C extension modules.
 
For category a), you are on your own.
For category b), you can use various methods in the gc module to print
out everything that is still 'live'. You can also recompile python to
build a list of all objects that are still live.
For category c), a tool like valgrind or purify often helps. Create a
simple example rather than trying to run it on your whole application.
 
 

________________________________

From: Michael Wieher [mailto:michael.wieher at gmail.com] 
Sent: Friday, March 14, 2008 10:16 AM
To: python-list at python.org
Subject: Re: Urgent : How to do memory leaks detection in python ?




2008/3/14, Pradeep Rai <              >: 

	Dear All,

	

	I am working on the python tools that process a huge amount of
GIS data. These tools encountering the problem of memory leaks. 

	

	Please suggest what are the different ways to detect the memory
leaks in python ?

	

	This is very critical problem for me. Help needed urgently.

	

	Thanks & Regards,

	Pradeep


Python doesn't have memory leaks.


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

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.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-list/attachments/20080314/5db43fc2/attachment-0001.html>