-
-
Notifications
You must be signed in to change notification settings - Fork 7.9k
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
[Windows 11] OBS crashes during regular Windows shutdown #10848
Comments
Duplicate of #10833? |
Btw I just tested it here and I didn't even had to stream to YT, just shutdown Windows 11 with OBS still open. "Safe Mode |
Possibly, there's not a lot of information in 10833 on what is causing it. Might be related, might not. |
I think it is related to this logic: Then, next time application is started, the sentinel file already exists, and unclean_shutdown is set to TRUE, and trigger the message present in the log, and also in the #10833 title. We should get a product decision: if this message is annoying and we want to get rid of it, let's think on a different approach rather than this sentinel file. I believe we should put this "delete_safe_mode_sentinel" as required action on application closure |
In the case of this issue (#10848), it was not merely a spurious an error dialog upon subsequent application launch (perhaps a false positive), but a genuine application crash (with an error dialog (invalid instruction executed) and a crash report) during the Windows shutdown process. In particular, an invalid instruction was executed thereby invoking a signal handler. See the attached crash report. Best |
Without streaming, I have also been able to consistently recreate this issue. It has become immensely frustrating to not be able to shut my computer down without first closing OBS as the crash handler blocks shutdown (separate issue, it probably shouldn't be able to do this.). |
Please provide a crash log. |
Are you logged into to YouTube via account connection in OBS Settings (Settings -> Stream)? Have you logged into the YouTube Control Panel for their additional browser docks? Do you have any other browser docks open? Just trying to narrow down a reliable set of steps to reproduce. |
In my case, I am logged into Twitch and use the chat, activity feed, and stream information panels docked. |
I know this isn't a high priority issue (which may not even be related to OBS code specifically) and while there is still more testing to do (a lot of which I am not sure how to approach yet), I think I was hopefully able to narrow down the problem at least some and thought it was enough to be worth sharing here. I was able to reproduce the same issue fairly easily on a system I setup, and long story short, I think it is related to Nvidia GPUs; more specifically recent driver versions and some interaction they have with the version of I first tried making it occur in both a Windows 10 and 11 VM running via VMware Fusion on a Mac, neither of which exhibited the issue. I then installed the most recent version of Windows 11 on an older physical system with a Sandy-Bridge-E Xeon and a GTX 760 in it, which is where some of the more interesting behavior began to appear. To begin, I used the older driver that Windows chose from Windows Update (it was one from 2020, although I can list the exact version if desired). NVENC was not available when using this driver, and when using the software H264 encoder, OBS reported no crash upon shutting Windows down while it was running. I then tried with the most recent driver for this GPU available on Nvidia's website (only receiving security updates), which made this issue appear. I first thought that it might be related to NVENC, but regardless of what encoding method is selected, it still crashed. Trying with a GTX 980 (on same driver version as most recent Nvidia GPUs) also produced the issue (both riidefi and partymanx also have Nvidia GPUs). Below is what/all I see appear on this system after it occurs Seeing that the error always seems to occur in a thread that is executing specific code inside
(The full log and crash report are also attached below) It always seems to halt at For now, this is as far as my testing has gone. Naively, it seems to be |
Operating System Info
Windows 11
Other OS
No response
OBS Studio Version
30.1.2
OBS Studio Version (Other)
No response
OBS Studio Log URL
https://obsproject.com/logs/krQyPY0gGII9KRai (previous log) https://obsproject.com/logs/qaOHGs2BO4ydjHpB (current log)
OBS Studio Crash Log URL
https://obsproject.com/logs/FqCrvAHYdESIIupf (crash)
Expected Behavior
I would expect the OBS application to cleanly close during a standard Windows shutdown interaction.
Current Behavior
A crash dialog appears noting the exception being raised in the OBS application.
Steps to Reproduce
Anything else we should know?
No response
The text was updated successfully, but these errors were encountered: