-
-
Notifications
You must be signed in to change notification settings - Fork 713
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Client app crashes OBS studio when client closes socket / terminates #626
Comments
Are you able to provide a crash log? |
Just encountered this too when working on a project that implements my own client connection to the websocket protocol.
( What is interesting, is that it doesn't seem to happen all the time, you can see me connecting and disconnecting as I'm working on my integration. Here is my full log as well: I'm not seeing a reference to a minidump though. 🤔 happy to follow some steps if you have a specific set you would like me to take. |
Issue type
Bug report
Description
Client application connects to OBS studio on the websocket port ( localhost:4444 tcp ipv4 ) and sends initial HTTP upgrade request over a blocking socket.
Client application then switches socket to non-blocking and uses epoll to wait for incoming data from OBS studio.
Websocket plugin sends HTTP upgrade response to client application and client application reads 156 bytes successfully into a buffer.
Client application then exits / terminates itself because its still under active development, which causes OBS studio to crash with the following output to the terminal:
The websocket plugin, because it is acting as a server, should expect a client application to terminate at any point in time and handle the socket closure / client disconnect gracefully, but instead it just crashes everything.
Steps to reproduce and other useful info
See above description for steps to reproduce.
Technical information
The text was updated successfully, but these errors were encountered: