-
-
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
Edge: After the last stream is disconnected, if the same stream is requested again within 3 seconds, it cannot be played smoothly. #2215
Comments
After investigation, it was found that too much time was consumed during
|
@winlinvip Upon further investigation, it was found that the 3-second delay caused by
|
I also encountered the same problem. The reason for the issue is similar to the original poster's. I searched on Git and indeed found someone who had encountered a similar problem. Changing the time of srs_usleep is not a good solution, as there still exists a window of time where the problem can occur, although the probability is relatively low.
|
@winlinvip
|
Description'
Please ensure that the markdown structure is maintained.
edge
origin
Replay
How to replay bug?
Steps to reproduce the bug:
Analyze the reason:
When the last stream is disconnected, it will go to
SrsPlayEdge::on_all_client_stop
, and then enterSrsEdgeIngester::stop
.At this point, when
trd->stop()
is executed, it takes about 3 seconds, and if there is a new stream request coming in, there will be a problem.Expected Behavior (Expect)
> Describe your expectation
Please describe what you expect to happen.
Hope that even if the last stream is disconnected, requesting the same stream again within 3 seconds can still play smoothly and normally.
TRANS_BY_GPT3
The text was updated successfully, but these errors were encountered: