mosh-chrome
mosh-chrome copied to clipboard
rpwoodbu
Unstable with lots of output
From a user on the Chrome Web Store:
After a while of using mosh seems to go to the state of not being connected, it seems to happen more often when there's more change with lots of output and when I'm not quite looking. At the top it displays mosh: Last reply 1:57 ago. [To quit: Ctrl-^ .] and the content of the display seems to be lagging behind and not accepting any input (I have other windows open with the same screen / emacs so I can see how much it lags behind.)
This is kinda peculiar. I haven't seen this, even though I use it all day every day. And I'm not immediately able to reproduce it. The symptoms remind me of some issues I had in initial development with select() emulation not working properly.
Any details on how to reproduce this reliably would be appreciated.
"Last reply" in particular means that the client is getting new frames from the server in a timely manner, but those frames don't acknowledge anything that the client has sent since however long ago. You might see this if the client's Wi-Fi downlink is working fine but not the uplink.
I had it every time I was doing live build, or a kernel compilation. Something with a lot of continuous output for a long time. Once it hit the state of not being connected, it will hold that state (even though output has stopped and traffic is low) until I press a key. It seems as if there is some counter overflowing (16 bits?) as if there have been 2^16 packets received without any return packets it reaches that state. This is on a arm exynos 5250 chromebook with wifi. BTW: with the current release (v0.2.8.30) I haven't been able to get that issue. I will update if I can get it again.
