- From: Timothee Besset <ttimo@idsoftware.com>
- Date: Wed, 30 Apr 2003 13:42:34 +0200
- CC: Richard Atterer <richard@list03.atterer.net>, www-lib@w3.org
Ok, so I can confirm that HTEventTerminate is the cause of the problem.
Since it kills the HWND, the socket is not freed, but it becomes
unusable. I suppose an HTEventTerminate should in turn trigger a cleanup
of all the things that depend on it? So consider this a bug report..
I fixed my timeout triggering crash by doing:
HTEventList_unregisterAll();
HTHost_setEventTimeout(-1);
instead of
HTEventTerminate();
Since that no longer kills the HWND, my WSAAsyncSelect bug is gone too..
TTimo
Timothee Besset wrote:
>
> I think I know why this is happening. But I am not sure about the way
> to fix it properly yet:
>
> After the first download, I call HTEventTerminate. On win32 this kills
> the HWND used for events, and used by the socket.
>
> I use HTEventTerminate to avoid my default timeout of 10 seconds to be
> called later on after the request is done and processed. This was
> causing a crash on win32. So maybe this fix is introducing more
> problems than it's fixing really. I will experiment some more.
>
> TTimo
>
> Richard Atterer wrote:
>
>> Hi,
>>
>> can you provide a more detailed trace of the libwww output?
>> Preferably with comments by you which explain what calls you are making.
>>
>> Cheers,
>>
>> Richard
>>
>>
>>
>
>
>
>
Received on Wednesday, 30 April 2003 07:42:46 UTC