You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Operating system and version: macOS 1.15.6
OBS Studio version: 24.0.6 (cannot upgrade to 25.x because of insanely high CPU usage see #2841 for that)
Expected Behavior
OBS works fine and does not crash.
Current Behavior
OBS reliably and reproducibly crashes on some events in other applications. First I thought it was random. But then I found stable reproducible pattern to that with 1Password (v7.x)
Steps to Reproduce
Have OBS running (recording or streaming or both) with an active display capture in ANY of the scenes
Have 1Password locked
On any screen (either captured or not -- does not matter) activate 1Password and type-in the password to unlock it
Hit enter (to unlock after typing-in the password)
Check OBS (it is gone, no stacktrace, no any notification, it is just gone the moment I hit enter to unlock 1Password)
Additional information
The text was updated successfully, but these errors were encountered:
The password crash is fixed in 25.0.8, it has to do with secure inputs. Please try the latest RC to see if performance is better. Otherwise, keep an eye on that other ticket.
@WizardCM can this fix be backported to 24.x? I tried 26-RC3 and it still high CPU there (I added my comment to the relevant ticket).
My concern is that 26.x will possibly still have performance issue on macos when released, in which case I am (and others) still stuck on 24.x. But we would need to make sure that things at least do not crash unexpectedly mid-stream or during the long recording session.
Platform
Operating system and version: macOS 1.15.6
OBS Studio version: 24.0.6 (cannot upgrade to 25.x because of insanely high CPU usage see #2841 for that)
Expected Behavior
OBS works fine and does not crash.
Current Behavior
OBS reliably and reproducibly crashes on some events in other applications. First I thought it was random. But then I found stable reproducible pattern to that with 1Password (v7.x)
Steps to Reproduce
Additional information
The text was updated successfully, but these errors were encountered: