-
-
Notifications
You must be signed in to change notification settings - Fork 5.4k
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
WebRTC: SRS 5 docker crash when RTMP2RTC over TCP. #3784
Comments
What browser are you using, what is your video source, does it always occur? If it does, could you please attach the video source file.
|
I used latest GoogleChrome on macOS. It only occurs after refreshing the browser, and not always occur just rarely. About the video source, it happened on several videos I tried, so I guess the issue could be at the browser refreshing which caused an error in the connection. I can see some related info in the above log. |
When the browser refreshes, it is possible to disconnect the TCP connection and then re-establish a new TCP connection. At this time, it is indeed possible to trigger boundary conditions. Please spend more time researching under what conditions it is more likely to occur, such as whether it is specific video content, a specific browser, or a specific operation method.
|
For #3505 SRS crashed at closing a active fd: void srs_close_stfd(srs_netfd_t& stfd)
{
if (stfd) {
// we must ensure the close is ok.
int r0 = st_netfd_close((st_netfd_t)stfd);
if (r0) {
// By _st_epoll_fd_close or _st_kq_fd_close
if (errno == EBUSY) srs_assert(!r0); |
Fixed, see #4083 |
Fix issue #3784 --- Co-authored-by: Jacob Su <suzp1984@gmail.com>
Description
While I was testing with rtmp to webrtc, the webrtc stream worked well. Then I refreshed the browser, and srs crashed
SRS Version: 5
SRS Log:
Replay
While I was testing with rtmp to webrtc, the webrtc stream worked well. Then I refreshed the browser, and srs crashed
Expect
Do not crash
The text was updated successfully, but these errors were encountered: