[Pymilter] memory leak in 0.9.2?

Stuart D. Gathman stuart at bmsi.com
Tue Jul 28 17:32:31 EDT 2009


On Tue, 28 Jul 2009, Stuart D. Gathman wrote:

> I guess I'm not likely to reproduce it here then.  I added a getdiag()
> method to the module.  It returns a tuple.  Currently, the first two
> elements are counts of contextNew and contextDel.  The counts are
> incremented and returned only with GIL locked (PyEval_AcquireThread).
> I'll test it, and then commit to CVS.

Tested and commited to CVS.  When running synchronously, del count
is always one less than new count.  When running asynchronously, they
get farther apart as more threads are active.

-- 
	      Stuart D. Gathman <stuart at bmsi.com>
    Business Management Systems Inc.  Phone: 703 591-0911 Fax: 703 591-6154
"Confutatis maledictis, flammis acribus addictis" - background song for
a Microsoft sponsored "Where do you want to go from here?" commercial.



More information about the Pymilter mailing list