Memory leak problems with python and COM

[Stefan Migowsky]

Hi,

you didn't miss the 131 build. This build was purely to test
against the developer version von Python 1.6. So the release
numbers would be ... 128, 129, 132 

   Stefan

>-----Original Message-----
>From: Etienne Labuschagne [mailto:etiennel at geospace.co.za]
>Sent: Monday, July 17, 2000 9:17 AM
>To: python-list at python.org
>Subject: Re: Memory leak problems with python and COM
>
>
>Hi there
>
>To my embarrasment I found that I am still using Python build 
>129 and that I
>(somehow) missed the release of build 131!
>
>Anyway, build 131 solved the problem!
>
>Thanks for your help.
>
>Regards
>Etienne
>
>"Mark Hammond" <mhammond at skippinet.com.au> wrote in message
>news:8klbu9$38u$1 at nnrp1.deja.com...
>> In article <963474833.835936 at proxy.lia.net>,
>>   "Etienne Labuschagne" <etiennel at geospace.co.za> wrote:
>> > Deleted a and b on the python side and then destroying the COM
>> server - that
>> > doesn't clear up the memory. I am using SafeArrayAccessData and
>> > SafeArrayUnlock on the server side to make sure that it 
>releases the
>> data on
>> > the server side.
>> >
>> > Is there something else that I must do?
>>
>> I suggest you get the latest CVS version (I realize this may be a
>> PITA :-(  Since build 132, a number of leaks have been 
>fixed.  There is
>> a very good chance that this particular leak was plugged previously.
>>
>> If not, I will definately look into this and plug it!
>>
>> Mark.
>>
>>
>> Sent via Deja.com http://www.deja.com/
>> Before you buy.
>
>
>-- 
>http://www.python.org/mailman/listinfo/python-list
>