Arno I will try, but I managed to make a test application reproducing the problem that I have.
The problem occurs only when I try to connect to an IP address that is not available, it will not have any problem when connecting to a valid IP address (Such as from a computer that is online) or to 127.0.0.1 I´m sending the source of my test application to your personal e-mail so you can test Eric -----Mensagem original----- De: TWSocket [mailto:twsocket-boun...@lists.elists.org] Em nome de Arno Garrels Enviada em: segunda-feira, 3 de junho de 2013 13:36 Para: ICS support mailing Assunto: Re: [twsocket] RES: RES: issues with wndcontrol's messagedispatchmechanism On Monday, June 03, 2013 6:05 PM [GMT+1=CET], Eric Fleming Bonilha schrob: > I use AVG here... > but since my fix actually fixed my issue, I think that something more > is involved.. Please Eric and Merijn, try to reproduce the issue on a clean computer without AVG or any other security software installed. A few years back a TWSocket user reported very strange errors to this list. It turned out that Kasperski AV was the problem. The only workaround was to remove the AV-program or to install an update. > I will try to make a test > application Thanks -- Arno > Eric > > -----Mensagem original----- > De: TWSocket [mailto:twsocket-boun...@lists.elists.org] Em nome de > Arno Garrels Enviada em: segunda-feira, 3 de junho de 2013 12:44 > Para: ICS support mailing > Assunto: Re: [twsocket] RES: issues with wndcontrol's message > dispatchmechanism > > On Monday, June 03, 2013 9:04 AM [GMT+1=CET], Merijn Bosma schrob: > >> Please see attached sources + executable (compiled with XE2). >> This reproduces well on both win8 64 bit and win7 32 bit. XP does not >> seem to have the same issues. > > Thanks, I'm trying your test case since 30 minutes on win7 64-bit > without any error (many times exited and program restarted also with > different IPs). > > 17:25:30:735 //////////////////////////////////////////// > 17:25:30:739 CLIENT - Connecting socket to 192.168.2.110 > 17:25:30:776 CLIENT - Connecting socket to 192.168.2.111 > 17:25:30:779 CLIENT - Connecting socket to 192.168.2.112 > 17:25:30:782 CLIENT - Connecting socket to 192.168.2.113 > 17:25:30:785 CLIENT - Connecting socket to 192.168.2.114 > 17:25:30:789 //////////////////////////////////////////// > 17:25:30:792 Starting timer > 17:25:30:795 //////////////////////////////////////////// > 17:25:38:795 CLIENT - Freeing sockets > 17:25:38:800 CLIENT - socket [12219024] disconnected (192.168.2.110), > error 0 > 17:25:38:805 CLIENT - socket [12221200] disconnected (192.168.2.111), > error 0 > 17:25:38:811 CLIENT - socket [12223376] disconnected (192.168.2.112), > error 0 > 17:25:38:818 CLIENT - socket [12225552] disconnected (192.168.2.113), > error 0 > 17:25:38:825 CLIENT - socket [12227728] disconnected (192.168.2.114), > error 0 > 17:25:38:833 SERVER - Starting socket server on port 5030 > 17:25:38:837 CLIENT - Connecting socket to 127.0.0.1 This socket might > eventually close.. lets wait and see > 17:25:38:842 CLIENT - client connected event [12225552]. IP = > 127.0.0.1 Error = 0 > 17:25:38:847 SERVER - Client connect ip: 127.0.0.1 error(0) > > Do you use any security software? > It won't be the first time that such software doesn't handle async > winsock API correctly. > > Maybe you and Eric do use the same AV-program? > > -- > Arno > > > >> >> Click the button: >> - some stuff is inited >> - 8 second timer is started >> - some more stuff is done >> - everything which happens after this seems to be manifestation of >> the issue. >> >> Normally it takes approx 20 seconds to see this after the button is >> clicked. If you have a hard time reproducing, changing the 5 ip >> addresses which the app connects to after you click the button might >> help. >> >> Hope you can reproduce, if you have questions, don't hesitate :) >> >> tschüss ;) >> >> Merijn >> >> >> >> On 3-6-2013 07:52, Arno Garrels wrote: >>> On Monday, June 03, 2013 7:23 AM [GMT+1=CET], Merijn Bosma schrob: >>> >>>> I have a simple one-click app which shows some aspect of the >>>> problem (unexpected drop, unexpected data, etc) at near 100% >>>> reproduction change. Should I put it on the mailing list or should >>>> I sent it directly? >>> The mailing list doesn't allow larger attachments. Please send the >>> source code to me via personal email. What windows version do you >>> use? > -- > 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 -- 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 -- 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
