-
Notifications
You must be signed in to change notification settings - Fork 99
OBS crashes in libswscale when starting with changed resolution #29
Comments
Let me know if I should build the tool with debug symbols to get a nicer stack trace. |
I have the same problems. Here the back trace: info: adding 23 milliseconds of audio buffering, total audio buffering is now 92 milliseconds (source: Mic/Aux) info: adding 23 milliseconds of audio buffering, total audio buffering is now 116 milliseconds (source: Mic/Aux) Thread 11 "video-io: video" received signal SIGSEGV, Segmentation fault. |
Interesting observation I had is that it seems to be something to do with the OBS config files. These steps got me predictable behavior.
I suspect it may be linked to OBS being unable to gracefully exit due to #10, I'm going to try to apply the patch for that issue and see if I can still reproduce. |
Applying #21 to allow OBS to exit gracefully seems to make the non-crash behavior persist across multiple launches. I suspect this doesn't actually solve the underlying issue (configs being corrupted causing a crash), but it makes it usable in 99.9% of situations. |
Hello, I had a problem today where OBS would crash when I started V4L2 Video Output, I can confirm that going on Settings and changing Base Canvas Resolution and Output Scaled Resolution to 1920x1080 solved the problem for me and I am now able to start V4L2 Video Output, without any problems. |
When the canvas/output resolution is set to 1920x1080, v4l2sink works fine. But when I stop, change the canvas/output resolution to 1620x1080 and then start v4l2sink again, OBS segfaults:
Not sure if this is related to #13.
The text was updated successfully, but these errors were encountered: