Closed daviewales closed 2 years ago
I'm having a similar issue on macOS 11.6.6 with OBS 27.4.2 and WS 4.9.1.
OBS is crashing in startup, and the logs end straight after the WSServer::start
line.
I've tried using 4.9.1, 4.9.1-compat, and the 5.0.0-beta, but the outcome is always the same.
Removing the plug-in solves the issue.
I'm having a similar issue on macOS 11.6.6 with OBS 27.4.2 and WS 4.9.1. OBS is crashing in startup, and the logs end straight after the
WSServer::start
line. I've tried using 4.9.1, 4.9.1-compat, and the 5.0.0-beta, but the outcome is always the same. Removing the plug-in solves the issue.
You appear to be having an unrelated issue. Please come to the Discord if you are still having issues, and we can help you look into it further.
Sorry, but 4.x versions are no longer supported. Yes this is an issue, but unfortunately we have no plans of providing any fixes. 10.13 is quite old at this point.
I'm having a similar issue on macOS 11.6.6 with OBS 27.4.2 and WS 4.9.1. OBS is crashing in startup, and the logs end straight after the
WSServer::start
line. I've tried using 4.9.1, 4.9.1-compat, and the 5.0.0-beta, but the outcome is always the same. Removing the plug-in solves the issue.
Update: seems this issue may have been caused by the Teleport plug-in. I had v0.4.1 installed, will test with the latest 0.5.0 release soon
Current hypothesis is its something to do with Teleport appearing as an active streaming session, which I discovered when opening the WS config dialog.
Operating System Info
macOS 10.13
Other OS
No response
OBS Studio Version
Other
OBS Studio Version (Other)
27.2.4
obs-websocket Version
4.9.1
OBS Studio Log URL
The program crashes before writing the details to the log. Log from Terminal included below.
OBS Studio Crash Log URL
The program crashes before writing the details to the log. Log from Terminal included below.
Expected Behavior
OBS should launch. Note that obs-websocket 4.8 does work.
Current Behavior
OBS crashed on launch after installing obs-websocket with the following error on the terminal:
Steps to Reproduce
Anything else we should know?
Full log below: