Open tt2468 opened 1 month ago
OBS does not de-initialize encoders on RTMP stream start fail
2. Configure an RTMP or WHIP stream with an invalid stream key/bearer token
Is it RTMP-only or it concerns RTMP and WHIP or any protocol (or even any encoded output) ?
I only validated this for RTMP and WHIP, though others are likely affected also. It seems as though the issue mainly stems from:
obs_output_signal_stop()
with a fail code, and never truly starts
Operating System Info
Windows 10
Other OS
No response
OBS Studio Version
30.1.2
OBS Studio Version (Other)
No response
OBS Studio Log URL
https://obsproject.com/logs/6iizipF9Li5buy3e
OBS Studio Crash Log URL
No response
Expected Behavior
If the stream output fails to start, allocated encoders should be de-allocated if they are not being used.
Current Behavior
The encoders sit initialized but not started, as
obs_output_begin_data_capture()
was never called. In the case of NVENC, this results in an NVENC session lingering around taking up a slot until OBS is shut down or a stream is successfully started.nvidia-smi:
Steps to Reproduce
Anything else we should know?
No response