davidjsherman
commented
7 years ago I think “trying to wait on more than 64 events” is aseba-community/dashel#14: there is a bug in the Windows implementation that will overflow the internal buffer. See my comment.
More generally, I agree that asebahttp needs to be made more robust. We lost precious time yesterday tracking down a connection error.
cor3ntin
Hello
I was testing ScratchX with Elisa and Joel when my asebahttp crashed completely. I took a printscreen here:
It is not easy to reproduce though... I was just manipulating the ScratchX program when it crashed. I will try to find a way to reproduce that. The program I did on ScratchX was a loop that turn on and off motors or LED to try to measure the time delay we had in these commands.
I was using