-
-
Notifications
You must be signed in to change notification settings - Fork 8.2k
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
Crash when livestreaming using SRT #10256
Comments
i need clear repro steps as i don't observe this at all; on the three machines you observe the issue, is it on the same network ? if it is, i'd suspect some router settings ? |
"After streaming smoothly for a while, the server stops receiving packets from OBS. At this point, OBS sometimes crashes directly, while other times it appears not to, but as soon as you click "Stop Streaming," it freezes completely, requiring manual process termination." Is there a possibility to get a memory dump where the process is frozen using .dmp file generated by windows? Could be helpful in troubleshooting the freezing of the process at least. |
We've updated libsrt in the beta to 1.5.3; as well as the avformat lib (from FFmpeg) which is used to mux to mpeg-ts format. I'll try to make more tests to trigger the bug. |
ps: pps: |
Now idk how much this would help, other than see exact location and memory state of OBS when it crashes. I personally do it directly through the Task Manager, it should be an option when right clicking the process in the active process list. Used preferably on a OBS Release build with debug info active. Steps to acquire dmp file:
To actually get something useful out of it I recommend using WinDbg to analyze it and see what's going on. by looking at the Call Stacks and memory fields, at the time of the crash. |
Not sure if my issue is exactly the same... I get 1 or just a few frames of video output. Output seems to continue to send, but I don't get any further video frames or more audio. Video preview continues to work. When I click "stop streaming" OBS hangs and I have to kill it. It does this every time so I should be able to repro easily. Will try to get a dump. Edit |
if you go back to obs 30.0, there's no issue ? |
That is correct. I go back to 30 and there's no issue at all. I've
changed nothing between versions related to my SRT config.
I'll get that stack trace today! Thanks!
|
If you are having this issue, please provide the full configuration of your SRT parameters (you can omit the domain/IP and port information). Please also provide the full information for your SRT server/receiver (software, version, parameter configuration), whether OBS and the server/receiver are on the same network or same PC (or different network/PC), and the relevant OBS log for the problem session. If you want to bisect the exact point at which dependencies changed, here are relevant commits (which point to different dependency versions) which should have CI artifacts available: |
I use ffmpeg in listener mode to output the OBS stream to a decklink interface. Listener command looks like this:
The
This is on a local wired 10 gig network, two different computers. Log file is here: https://obsproject.com/tools/analyzer?log_url=https%3A%2F%2Fobsproject.com%2Flogs%2FGOstBEY5U66LqsOS#logURL Sorry for the amount of sources 😅 Please keep in mind that I can go back to OBS 30 and run without issues. |
This is what I got: https://gist.github.com/thelegendtubaguy/3266ef0b4920345b10a93ebe23a4de06 |
Rytoex has a stack trace which seems to point to a libsrt bug introduced in 1.5.3 which has later been fixed @thelegendtubaguy @Abeja27 @laurfb Could you test by replacing srt.dll in bin folder with these? |
Yes, been running for 10 min. already. Thx! |
Hi again. |
That fixes it for me! I can't get it to exhibit the same behavior as before. Either in lots of short term tests or streaming for tens of minutes, where previously it could not. |
Fixed for me too. I couldn't reproduce it again after 2 hours of testing. @RealIndrit I'm sorry, you asked me the dump files but I didn't have any time these days. Too late now I guess. Thank you guys your fast support. |
Thanks for the feedbacks. |
To clarify, I only got this to freeze once during some brief testing. I haven't had OBS outright crash from it. If there's a separate crash scenario, I haven't found it yet. |
Operating System Info
Windows 10
Other OS
No response
OBS Studio Version
30.1.0-beta1
OBS Studio Version (Other)
No response
OBS Studio Log URL
https://obsproject.com/logs/FOhy1iAx3mvWB7Gr
OBS Studio Crash Log URL
https://obsproject.com/logs/QCCBqe12ciKu0RWR
Expected Behavior
Being able to live stream using SRT without any issues.
Current Behavior
After streaming smoothly for a while, the server stops receiving packets from OBS. At this point, OBS sometimes crashes directly, while other times it appears not to, but as soon as you click "Stop Streaming," it freezes completely, requiring manual process termination.
Steps to Reproduce
Anything else we should know?
This problem seems to be related to #9438. That issue was still happening to me until this version when finally no packets are lost at all. However that was replaced for the crash/freezing that I'm reporting now.
The previous issue was closed at the time, and I didn't have time to continue investigating. The only discovery I made is that the problem worsens significantly when setting the SRT option "sendbuf" to a high value. With small values, there were almost no lost packets, but it wasn't a viable workaround as the effective bitrate decreased due to the small buffer size. In this version, I'm unsure if that option has any impact anymore.
It would be great to know the exact commit where the behavior changed. Do you have any idea which one could I check? I wouldn't like to test one by one.
I would be great If you could reproduce it but that wasn't the case with #9438. Maybe it could be related to some specific hardware or configuration, but after testing different configurations in 3 machines It could find the issue. Ask me for any further information you may need.
Thank you for your time.
The text was updated successfully, but these errors were encountered: