New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 730022 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 731679
Owner: ----
Closed: Jun 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Chrome , Mac
Pri: 2
Type: Bug



Sign in to add a comment

SetRemoteDescription sometimes failed with the WARNING:stream not found for ssrc ...

Reported by brightc...@gmail.com, Jun 6 2017

Issue description

UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3029.110 Safari/537.36

Steps to reproduce the problem:
1. Add ssrc to remote sdp and set local/remote 
2. after a while, delete this ssrc and set local/remote
3. repeat 1 and 2, This will success most of time, but will failed sometimes 

What is the expected behavior?
Sucess every time

What went wrong?
SetRemoteDescription failed with the following warning in chrome log:
Stream not found for ssrc: xxxxx
Failure in SetRemoteContent with action 2
Failed to set Failed to set remote answer sdp: Session error code: ERROR_CONTENT. Session error description: Failed to set remote video description streams

Did this work before? N/A 

Chrome version: 58.0.3029.110  Channel: n/a
OS Version: OS X 10.12.4
Flash Version: 

ssrc is assoicated a receive stream, I wonder the action taken by webrtc when:
1. If the receive stream never reached
2. If the receive sream ever reached, but stopped and wait a while to delete it
 
Components: Blink>WebRTC>PeerConnection
Labels: OS-Chrome OS-Linux OS-Windows
Cc: deadbeef@chromium.org
Components: -Blink>WebRTC>PeerConnection Blink>WebRTC>Network
deadbeef@: 
At first sight, it looks like a lower-level WebRTC issue to me. If you think this is not the case, bounce back to Blink>WebRTC>PeerConnection
Hello All,

This problem occured more often with chrome version 59. I can confirm that the ssrc has associated stream was displaying and was just stopped by far end.   
I inpect the source code.why not let the setremotedescription scucess? Even the stream not found for ssrc: xxxxx when remove ssrc from remote SDP? This will not have any site effect.
When a remote ssrc is need to be deleted, the following is the calling paths: 
WebRtcSession::SetRemoteDescription->WebRtcSession::UpdateSessionState->WebRtcSession::PushdownMediaDescription->BaseChannel::PushdownRemoteDescription->BaseChannel::SetRemoteContent->VideoChannel::SetRemoteContent_w-> BaseChannel::UpdateRemoteStreams_w->BaseChannel::RemoveRecvStream_w->WebRtcVideoChannel2::RemoveRecvStream, the WebRtcVideoChannel2::RemoveRecvStream is failed with "Stream not found for ssrc: xxxx", then all the callings in the path return false caused setRemoteDescrition failed. I wonder:
It means that this ssrc has no associated receive video stream and I think this issue is very popular,i.e: no associated stream with this ssrc is never reached. I suggest we should not make SetRemoteDescription failed under this condition.     

Labels: Needs-Feedback
Hmm. RemoveRecvStream should only be called if AddRecvStream was called previously so I'm not sure how this could happen. It could be that you're hitting this bug, which was fixed pretty recently: https://bugs.chromium.org/p/webrtc/issues/detail?id=7725

Could you try updating to a later revision where  issue 7725  is fixed? If you still see the issue, could you gather a native webrtc log (https://webrtc.org/native-code/logging/)?
Thanks you very much. Very similar, I will try! Which revision is fixed? 
Project Member

Comment 8 by sheriffbot@chromium.org, Jun 10 2017

Labels: -Needs-Feedback
Thank you for providing more feedback. Adding requester "deadbeef@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Hello All,

The fixed bug is effective. I wonder when the fixed will be accepted in chrome browser?  
Mergedinto: 731679
Status: Duplicate (was: Unconfirmed)
Merge is being requested in the linked bug.

Sign in to add a comment