While in any game, holding down the close window button will cause the client to hang until released. Everything physics-based on the client (Character updates, NetworkOwned parts) will stop recieving updates and freeze in place until the button has been released.
The client will not close until the mouse is released on the button itself.
To my knowledge, there is no reasonable method of detecting this.
- Delta times, if a player is on mobile/low end pc and we give them a lot to do, we can see frame loss that could trigger this
- Poor code starting to run could have clients falsly identified as doing this too.
.
Brief examples of this
-
The client still appears to be given everything it needs, it just doesn’t do anything with it until we resume
https://i.gyazo.com/af5cfae04d6c0177e8ca91679ab156aa.mp4 -
Freezing the client’s physics (My client appears to have recieved a velocity update, but not acted on it until I released my mouse. Until then, I am completely frozen.)
While not a huge bug, it’s difficulty to detect and its ease to reproduce can cause issue across a number of games.
I’ve noticed this issue a few months ago, but didn’t think it actually did anything. I’m unsure as to how long it has existed for.