Sorry for the late reply, we've had an expo this week which needed some (a lot) of attention.
I didn't find any calls to ProcessMessages(). This socket runs in it's own thread, so a call to ProcessMessages() would have been out of place. I did find something else though. Even though the server socket had it's MultiThreaded property set to true, the client socket it spawns did not have this property set to true explicitly. Therefor ICS was calling ProcessMessages() itself now and then. Maybe it would be a good idea to let TCustomWSocketServer set Multithreaded of newly created clients to the same value it has itself? WSocketS.pas around line 360. Anyway, back to my problem, because it's still here :| All sockets have now their MultiThreaded property set to true. I removed the wsoNoReceiveLoop again, because it didn't seem to have to do anything with the problem. I've added some logging when the problem occurs, so I have some new information. The OnDataAvailable event is never triggered from within itself. So it seems not to be caused by calling a messagepump in the event, which triggers the event again! If in the loop, in each event there is no data to receive. If in the loop, in each event, error = 0 If in the loop, in each event I note LastError before, and after I call ReceiveStr(). I do this because TCustomWSocket.ASyncReceive, which triggers the event, looks at FLastError to decide it should call the event again. In both cases I had the extended logging, LastError was set to a non-zero value. In the first case it was 10054, and the second case it was 10034. LastError was the same before and after the call to ReceiveStr(). Besides the extended logging, I built in a mechanism which automatically dumps a call stack of the thread the socket runs in, 60 seconds after I get stuck in the 'loop'. Of course this call stack is just a snapshot somewhere in the loop, but since I got the same call stack a couple of times now, I'm pretty sure this is how the OnDataAvailable event is triggered. The strange thing is, that there always seems to be a strange 'jump' in the call stack which I can't explain (or probably which I don't understand): It goes from Do_FD_READ to AsyncReceive (normal), but before AsyncReceive is actually run, it jumps to TriggerDataSent (?). After that some other strange things in the call stack. See the call stack here, the calls to "CheckForPendingMessages" are calls to methods which call the messagepumps for different controls, amongst which TCustomWSocket.ProcessMessages(). I really hope someone can give me some more pointers in the right direction! callstack: |7C90E9FD|ntdll.dll | | |NtWriteFile | | |7C810E10|kernel32.dll| | |WriteFile | | |006C268B|AviaVox.exe |ServerTimedSocket.pas |TServerTimedSocket |_Log |291 | |006C2528|AviaVox.exe |ServerTimedSocket.pas |TServerTimedSocket |_Log |275 | |006C27DB|AviaVox.exe |ServerTimedSocket.pas |TServerTimedSocket |OnDataAvailable |305 | |005CBFA0|AviaVox.exe |WSocket.pas |TCustomWSocket |TriggerDataAvailable |5970 | |005CBF80|AviaVox.exe |WSocket.pas |TCustomWSocket |TriggerDataAvailable |5946 | |005CDA0B|AviaVox.exe |WSocket.pas |TCustomSocksWSocket |TriggerDataAvailable |6504 | |005CD9E0|AviaVox.exe |WSocket.pas |TCustomSocksWSocket |TriggerDataAvailable |6502 | |005CE90C|AviaVox.exe |WSocket.pas |TCustomLineWSocket |TriggerDataAvailable |7065 | |005C8C58|AviaVox.exe |WSocket.pas |TCustomWSocket |ASyncReceive |4204 | |005C6DB3|AviaVox.exe |WSocket.pas | |WSocket_Synchronized_ioctlsocket|2136 | |005C6D8C|AviaVox.exe |WSocket.pas | |WSocket_Synchronized_ioctlsocket|2133 | |005C8CDD|AviaVox.exe |WSocket.pas |TCustomWSocket |ASyncReceive |4226 | |71AB42F5|WS2_32.dll | | |send | | |71AB42FC|WS2_32.dll | | |send | | |005C6CF7|AviaVox.exe |WSocket.pas | |WSocket_Synchronized_send |2098 | |005CBEDC|AviaVox.exe |WSocket.pas |TCustomWSocket |TriggerSendData |5907 | |005C87A9|AviaVox.exe |WSocket.pas |TCustomWSocket |RealSend |3976 | |005C41D0|AviaVox.exe |WSockBuf.pas |TBuffer |Peek |212 | |005C882E|AviaVox.exe |WSocket.pas |TCustomWSocket |TryToSend |4006 | |005C89AB|AviaVox.exe |WSocket.pas |TCustomWSocket |TryToSend |4070 | |7E41CBB3|USER32.dll | | |PostMessageA | | |7E41CB69|USER32.dll | | |PostMessageA | | |005C8BB9|AviaVox.exe |WSocket.pas |TCustomWSocket |Send |4164 | |005C8C0D|AviaVox.exe |WSocket.pas |TCustomWSocket |SendStr |4177 | |006C2A54|AviaVox.exe |ServerTimedSocket.pas |TServerTimedSocket |OnOutgoingEncryptedData |352 | |006C2A7E|AviaVox.exe |ServerTimedSocket.pas |TServerTimedSocket |OnOutgoingEncryptedData |355 | |7C90D8ED|ntdll.dll | | |NtDeviceIoControlFile | | |005C41D0|AviaVox.exe |WSockBuf.pas |TBuffer |Peek |212 | |005C882E|AviaVox.exe |WSocket.pas |TCustomWSocket |TryToSend |4006 | |7C9010ED|ntdll.dll | | |RtlLeaveCriticalSection | | |005C89AB|AviaVox.exe |WSocket.pas |TCustomWSocket |TryToSend |4070 | |005C89D0|AviaVox.exe |WSocket.pas |TCustomWSocket |TryToSend |4073 | |005CC047|AviaVox.exe |WSocket.pas |TCustomWSocket |TriggerDataSent |5985 | |005C8C1C|AviaVox.exe |WSocket.pas |TCustomWSocket |ASyncReceive |4198 | |005C8DA2|AviaVox.exe |WSocket.pas |TCustomWSocket |Do_FD_READ |4259 | |005C908F|AviaVox.exe |WSocket.pas |TCustomWSocket |WMASyncSelect |4394 | |005C8F38|AviaVox.exe |WSocket.pas |TCustomWSocket |WMASyncSelect |4332 | |005C7B7D|AviaVox.exe |WSocket.pas |TCustomWSocket |WndProc |3290 | |005C7B54|AviaVox.exe |WSocket.pas |TCustomWSocket |WndProc |3286 | |005CE46B|AviaVox.exe |WSocket.pas |TCustomLineWSocket |WndProc |6824 | |005C7CB5|AviaVox.exe |WSocket.pas | |XSocketWindowProc |3341 | |7E4196B2|USER32.dll | | |DispatchMessageA | | |7E4196A8|USER32.dll | | |DispatchMessageA | | |005C7D27|AviaVox.exe |WSocket.pas |TCustomWSocket |ProcessMessage |3388 | |005C7CE8|AviaVox.exe |WSocket.pas |TCustomWSocket |ProcessMessage |3380 | |005C7D3C|AviaVox.exe |WSocket.pas |TCustomWSocket |ProcessMessages |3402 | |005C7D34|AviaVox.exe |WSocket.pas |TCustomWSocket |ProcessMessages |3401 | |006C2121|AviaVox.exe |ServerTimedSocket.pas |TServerTimedSocket |CheckForPendingMessages |177 | |006C210C|AviaVox.exe |ServerTimedSocket.pas |TServerTimedSocket |CheckForPendingMessages |173 | |0061F5B5|AviaVox.exe |NetworkMaster.pas |TNetworkMaster |CheckForPendingMessages |600 | |0061F580|AviaVox.exe |NetworkMaster.pas |TNetworkMaster |CheckForPendingMessages |592 | |0061AA99|AviaVox.exe |networkComm.pas |TNetworkComm |CheckForPendingMessages |380 | |0061AA74|AviaVox.exe |networkComm.pas |TNetworkComm |CheckForPendingMessages |372 | |0061AC26|AviaVox.exe |networkComm.pas |TNetworkCommThread |Execute |424 | DZ-Jay wrote: > On Apr 11, 2008, at 03:39, Merijn Bosma wrote: > > >> In case I am, could that explain this behavior? >> I'm not calling the message pump when I'm receiving no data, so >> shouldn't that break the loop if it was there? >> > > You also may want to trace deep into all the procedures you call from > the event handler to see if any of them ultimately call the message > pump. > > dZ. > > > -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be