In cases of highly concurrent clients, there seems to be some bugs when disconnecting and still trying to write to the closed websocket connection or to the internal channels used. These added checks should hopefully prevent most of those panics. 🤞
In cases of highly concurrent clients, there seems to be some bugs when disconnecting and still trying to write to the closed websocket connection or to the internal channels used. These added checks should hopefully prevent most of those panics. 🤞
For some reason this was more prevalent when using gorilla/websocket v1.5.1 instead of v1.5.0 (https://github.com/andreykaipov/goobs/pull/64).
Also changes most of the DEBUG logs to TRACE logs.