Bug Report OBS Studio random FD_Close errors from different streamers.

R

ReaverStreamTeam

New Member
Hello we are in a 60 person Overwatch stream team and some of us thought it would be a great idea to switch to OBS Studios despite our team leader and several admins telling us otherwise because Classic actually works.

This week we have been filled with random disconnects from our streams for no reason, nothing else disconnects or even lags. We all have different internet companies and stream with different settings from 2500 bitrates to 6000 bitrates and the only thing we all had similar with our OBS logs are

Aborting due to FD_CLOSE, error 0
or
Aborting due to FD_CLOSE, error 10053

Note, we have never had these issues in OBS Classic and those that switched back to Classic haven't had issues since so, what is buggy with Studios that it can't stay connected and how soon can you fix it.

And yes we have read your little disconnect guide here https://obsproject.com/forum/threads/dropped-frames-disconnecting-lag-read-this-first.8870/ and it actually helps no one when it is YOUR software being buggy and not on our end (again when PARTNERED STREAMERS tell you to use Classic because it works better then OBS Studios then maybe you guys should look over your coding and fix the issues and get actual streamers to do a 3 to 6 hour test run where they actually stream.)
 
Perhaps try enabling the new networking code in settings -> advanced and see if that makes a difference.
 
Can you get us a full OBS log that shows the disconnect issues, with the "New network code" option enabled? This option includes a bit more detailed logging when it comes to network-related issues, and might shed some light on what's going on.

However, please keep in mind that we have millions of people who use OBS Studio. The network code between Classic and Studio is not the same, and those error messages are exactly what we see when there is a network connection failure between the PC that is streaming and the streaming service. We run into these kinds of issues on a daily basis, and we take every single one seriously. However, to date, there has not been a single report that has resulted from a bug in OBS itself, outside one single use case: Using the "New network code" options with the AMF encoder. We are aware of that bug (which only limits bitrate to 1000, and does not cause disconnects), and it will be corrected in the next release.
 
Since you're using the new network code, it's actually the same as classic, so nothing to do with the code.

Aborting due to FD_CLOSE, error 0

This means Twitch disconnected you. Your connection probably dropped and you didn't send any data, they will close idle connections after 5 - 10 seconds.​

Aborting due to FD_CLOSE, error 10053

This means your OS closed the connection, likely due to a timeout or maximum retransmissions reached. In both cases, it points to a problem with maintaining a stable connection to Twitch.​

As the author of the new network code, I've extensively tested it with week long streams and on a normal functioning connection there are no known issues. In any case, you should include a log file for more detail.
 
"
Aborting due to FD_CLOSE, error 10053

This means your OS closed the connection, likely due to a timeout or maximum retransmissions reached. In both cases, it points to a problem with maintaining a stable connection to Twitch."

Then the fault is WINDOWS or ISP?
 
You must log in or register to reply here.
Back
Top