| Graham Dumpleton 2006-10-19, 7:13 am |
| Comments below.
On 19/10/2006, at 8:55 PM, Graham Dumpleton wrote:
[vbcol=seagreen]
> For such issues, by all means just send the email direct to the
> mailing list.
> I have copied this back onto the list and I'll do some research
> into what
> you describe.
>
> BTW, I don't use Windows, but there are others on the list who do
> and it
> may help if you can explain what methodology you are using to see the
> Win32 handle leaks. This will help others to replicate it and then
> track it
> down.
>
> Thanks.
>
> Graham
>
> On 19/10/2006, at 8:50 PM, Jeff Robbins wrote:
>
Still looking at this, but where you do it looks to be wrong. The
documentation
below for PyThreadState_Clear() says:
The interpreter lock must be held.
Where you are calling that function, it isn't. It may need to be
moved to before
the call to PyEval_ReleaseThread(). Yes/No?
[vbcol=seagreen]
Graham
|