obs-studio
obs-studio copied to clipboard
obsproject
「BUG」Can‘t Exit OBS When Ruuing Replay
Current Behavior
When start the replay butter,can't exit the progarm.
Steps to Reproduce
1.Open OBS Studio 24.0.2 2.Start the replay butter button 3.Then minisize the window 4.Right clik the tray icon to select exit 5.Clik ''YES'' button in the next step
Additional information
After these step.The progarm was be closed. But the tray icon is still there.It's still working. Also can't open the new OBS and can't right clik the tray icon.
Can you please provide a log file from when this issue occurs? I am not able to replicate on my end.
Can you please provide a log file from when this issue occurs? I am not able to replicate on my end.
19:37:53.108: ==== Shutting down ==================================================
19:37:53.117: Switched to scene '(null)'
19:37:53.123: WASAPI: Device 'XIBERIA MG-1 (Realtek High Definition Audio)' Terminated
19:37:53.130: WASAPI: Device 'NetEase Music (Realtek High Definition Audio)' Terminated
19:37:53.136: WASAPI: Device 'Mix/Technica (Realtek High Definition Audio)' Terminated
19:37:53.141: All scene data cleared
19:37:53.141: ------------------------------------------------
19:37:53.151: Output '回放缓存': stopping
19:37:53.151: Output '回放缓存': Total frames output: 37361
19:37:53.151: Output '回放缓存': Total drawn frames: 37378 (37379 attempted)
19:37:53.151: Output '回放缓存': Number of lagged frames due to rendering lag/stalls: 1 (0.0%)
19:37:53.152: Video stopped, number of skipped frames due to encoding lag: 1/37377 (0.0%)
Then you try to exit OBS with an output active, it prompts you to exit:
This dialog is likely just opening behind another window. No bug.
In the future, please submit support requests through the appropriate channels.
On further testing, I was able to replicate this, but I'm not sure the exact steps to cause it to happen. It seems to be somewhat random.
I'm also experiencing this, and yes it does appear to happen at random.
Is there a way I can help here? Is there a method to have OBS provide more verbose logs? (I mean, more verbose than --verbose, which is less informative than I'd like) Since mine fails about half the time, it wouldn't take me long to provide logs which pin it down.
More info on this: TL;DR I can't disable the systray icon. It's not enabled, but there it is.
Noticing that OP mentioned that a necessary step was to minimise to the tray, I decided to disable the systray for the time being. (also noticed this was reported back in 24.0.2, I'm on 24.0.3. I started the app, unchecked the box, clicked OK, the systray icon disappeared, and exited as normal. Started again to test, and the systray icon is there. Go into settings, box is unticked. I have to tick to enable it, hit OK (not 'apply'! That's not good enough for it to work) and then go into settings and untick the box and hit OK (not apply), every time I launch, to make the systray icon go away. I've confirmed that my changes are making it into the settings file, even when I only hit apply (which does not apply those settings) I figured it has to be something wrong with my settings so I delete them all (backed up first of course).... and it works like this out of the box. Start with an empty obs-studio directory, say no to autoconfig, disable systray....As soon as I start recording, systray icon appears and it doesn't go away when I stop recording (although the red dot disappears)
Not sure if this is a separate bug but it strikes me that it might just fall under the same umbrella.
PS This might have been around for a while.... Just in case you're digging through commits.... https://www.reddit.com/r/obs/comments/8a4rvt/after_latest_update_tray_icon_wont_go_away/
PPS Another mention of the "won't close because replay buffer is running" thing: https://www.reddit.com/r/obs/comments/epu2pr/obs_not_closing_correctly/
Small follow up:
After hitting apply the taskbar tray icon choice will take place on either OK or Cancel, this seems working as intended (after Apply the pending changes cannot be Cancel'ed). I agree it probably should take affect on Apply and im not sure why it waits until the dialog is closed to update.
I caught this (or a similar issue?) on the debugger but am basically brand new to the code, so I'm not sure what the right fix is.
The main thread is waiting on Replay Buffer's stopping_event to be signaled. In obs_output_actual_stop, force is true, and delay_active is false, so it falls into the call_stop case which calls out to ffmpeg_mux_stop(). For some reason it never gets the stopping_event signal, so just hangs out.
My (100%) reproduction steps on Windows 64 are as follows:
- Choose Start Recording
- Choose Start Replay Buffer
- Click the Pause icon next to stop recording.
- Close the popup and click Exit, OR right-click the tray icon, choose Exit
- Click Yes
Experiencing this after updating to 28 and popped by to report the regression, but perhaps it's just still there from before....
Steps to reproduce:
- Download fresh OBS from https://github.com/obsproject/obs-studio/releases/download/28.1.2/OBS-Studio-28.1.2-Full-x64.zip and unzip it somewhere temporary (I used the desktop)
- Create a shortcut to obs64.exe and add --portable --startreplaybuffer
- Start OBS from said shortcut, and complete the wizard preferring recording and (I doubt this part is important, but for completeness, this was my process) using the largest desktop's size as canvas size and 60FPS as framerate.
- Complete the wizard, open settings, Enable: Replay buffer, minimize to tray when started, Disable: warn when active outputs
- Exit OBS and then start it up using the shortcut above
- Right-click the tray icon and select Exit.
- Hang. Process is still running, tray icon is visible, but the application is unresponsive.
Logs of these two startups (probably only the second one, where it crashes, is of interest, but both for completeness) Setup: 2022-11-20 18-19-51.txt Start and exit/hang: 2022-11-20 18-20-59.txt
Since the analyzer suggests them both, I should add that HAGS and admin have no effect here.