search

rpwoodbu / mosh-chrome

Mosh for Chrome
GNU General Public License v3.0
371 stars 59 forks source link

UI freezes? #181

Open IamCarbonMan opened 6 years ago

IamCarbonMan commented 6 years ago

Starting a few days ago, the terminal seems to have trouble updating. At first I thought it was network lag, so I used another terminal and Mosh client and connected to the same tmux window. When I typed on the Chrome Mosh client I could see it in the other terminal but the UI of the terminal seemed to be frozen. Alt-tabbing or opening and closing the Start menu seems to update this somehow; if the terminal isn't updating then alt-tabbing may cause it to update, sometimes when it's working fine alt-tabbing causes it to stop.

rpwoodbu commented 6 years ago

Am I to assume you're running the "native" Windows app?

IamCarbonMan commented 6 years ago

If by native you mean the Mosh Chrome App, then yes: https://chrome.google.com/webstore/detail/mosh/ooiklbnjmhbcgemelgfhaeaocllobloj?hl=en

rpwoodbu commented 6 years ago

You're running the app in regular Chrome, then? (That's deprecated, BTW... didn't know it even still worked outside of Chrome OS).

I have seen issues whereby Mosh for Chrome will stop updating, and it is fixed by typing into the window. I would be surprised if it were also fixed by more external influence, but it may be possible.

Next time it happens, can you try typing into the window (one keystroke will do) instead of switching focus? That will help me know if it is the same problem.

vapier commented 6 years ago

didn't know it even still worked outside of Chrome OS

app syncing is fun. if you have it already installed, Chrome won't uninstall it on you because that'd upset a ton of users. and if you install it on CrOS, it'll sync to your non-CrOS devices :).

wrt this bug report, i've seen a few for Secure Shell but haven't been able to reproduce it. i think it comes up when they suspend+resume, then the connection appears to be broken, but it turns out everything they typed was transmitted to the remote side. not sure where it's failing in the chain of events though ...