TCP socket events get lost

[Stu Redman]

I noticed aMule performs poorly with current wx SVN in Windows.
It works in principle, but most TCP network connections fail and clients appear to be unreachable. aMule works fine with wx 2.8.12 or wx SVN in Linux.

Kry suggested to try to revert 64565, and this fixes the problem. So this change apparently makes wx ignore a lot of valid events.

Platform is Windows 7 x64.

[Kry]

I am working on this as we speak, along with other wxSocket needed changed to address the rest of the tickets.

This problem in particular, which was caused by a patch introduced to solve a different ticket, is taking a bit to analyze as I want to undo the patch and fix the underlying reason for the previous ticket ( #11528 )

[vadz]

Unfortunately I don't know how to fix this neither. Just reverting r64565 is a bad idea as it would make the bug fixed by it reappear. And I also am not sure how exactly does it fix the problem, if there is nothing to read on the socket, what do we need the notification for?

It would be great to be able to reproduce this problem in the socket sample somehow. Without this I don't know how are we going to be able to debug it... Could you please let us know what is special/different from the sample about aMule and in which conditions exactly is this missing notification important?

[Stu Redman]

I retried aMule with wx 2.9.3, and here it works fine without reverting the changeset. No idea what change caused the different behavior.

[vadz]

OK, thanks for testing.