Re: [eboard-devel] {BUG eboard 1.1.1} eboard loses movestate on connection loss
Brought to you by:
bergo
From: Luuk v. d. D. <luu...@gm...> - 2011-08-16 16:44:42
|
Simon, thank you for the elaborate answer. I too found the infinite-loop bug when leaving eboard, FICS disconnects and eboard eats all CPU. I'll try the 'refresh' command. Luuk -----Original Message----- From: Simon Valiquette <v....@ie...> To: Luuk van der Duim <luu...@gm...> Cc: ebo...@li... Subject: Re: [eboard-devel] {BUG eboard 1.1.1} eboard loses movestate on connection loss Date: Tue, 16 Aug 2011 12:19:26 -0400 Luuk van der Duim un jour écrivit: > Hello, > > When playing on FICS and when my wireless network connection fails and > needs to be re-established, eboard gets confused and makes my clock run > but I cannot move. Resulting in lost games and a frustrated user. > > Any suggestions? You can try the command « refresh »; it sometimes works and won't makes the situation worst. For what it's worth, I believe it is related with a similar problem where there is confusion between FICS and eboard. There seems to be a race condition, which should'nt surprise anyone that ever picked a look at the eboard networking code (I had to after it stopped working on PowerPC, and some of the hack seems to work only by sheer luck). This race condition show up more often when there is lag, and give exactly the same symptoms you reported and usually the only solution is to disconnect and reconnect to FICS, and sometime only restarting eboard will do it. Probably related to that bug, eboard will usually reach an infinite loop if you let it open until FICS disconnect it. I think those 3 problems are all related, and the real solution would be to rewrite large parts of the networking code so as to have a clean, portable, much more stable (and maintainable) code. I never bothered to try, partly because I've been told (maybe 2 years ago) that the author planned to eventualy rewrite eboard, but it seems it never happened, or if it did then it took a new name. Sorry for giving you an explanation instead of a solution, but for now that is all I have to offer you unless someone have time to fix/rewrite the networking code. Simon Valiquette |