Re: [Python-Dev] Problems with the Python Memory Manager

2005-11-25 Thread Armin Rigo
Hi Jim, You wrote: (2) Is he allocating new _types_, which I think don't get properly collected. (Off-topic) For reference, as far as I know new types are properly freed. There has been a number of bugs and lots of corner cases to fix, but I know of no remaining one. This assumes that the

Re: [Python-Dev] reference leaks

2005-11-25 Thread Michael Hudson
Neal Norwitz [EMAIL PROTECTED] writes: There are still a few reference leaks I've been able to identify. I didn't see an obvious solution to these (well, I saw one obvious solution which crashed, so obviously I was wrong). When running regrtest with -R here are the ref leaks reported:

Re: [Python-Dev] reference leaks

2005-11-25 Thread Neal Norwitz
On 11/25/05, Walter Dörwald [EMAIL PROTECTED] wrote: Can you move the call to codecs.register_error() out of test_callbacks() and retry? It then leaks 3 refs on each call to test_callbacks(). n -- import codecs [24540 refs] [24541 refs] def handler(exc): ... l = [u%d %