chrome only error with websockets
error that only occurs in google chrome and is not restricted to our project. while idling, "WebSocket is already in CLOSING or CLOSED state." is thrown randomly. error can't be fixed, maybe a workaround using rejoin () can be implemented on the frontend to make experience for chrome users better.
Edited by Sven Kuffer