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

Issue 841686 link

Starred by 5 users

Issue metadata

Status: Archived
Owner:
Last visit > 30 days ago
Closed: Dec 20
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug


Show other hotlists

Hotlists containing this issue:
Chrome-Bug-Cleanup


Sign in to add a comment

Bob: video chat connection lost randomly

Project Member Reported by agnescheng@chromium.org, May 10 2018

Issue description

Reported from the field, hangout or appear.in video chat disconnected randomly. 

Release version: R65 and R66 10452.85.0


The issue can be duplicated as follow procedure:
1. Connect several DUTs (Bob) to the same AP, 
2. Use one of the DUT to create a chat room at https://appear.in( or Hangout).
3. Connect these DUTs to the same appear.in meeting( or Hangout).
4. After certain time, some  DUT started to disconnected from the meeting randomly <--- problem.

WiFi is still connected when the problem happens.

Reconnecting to the video call can work, but get randomly disconnected soon after.

Please find the logs in https://buganizer.corp.google.com/issues/78315388#comment13
 
Components: Blink>WebRTC>Network
Components: Blink>WebRTC>Video

Comment 3 by sprang@chromium.org, May 11 2018

The logs contains of warnings like

[1:52:0507/151923.362641:WARNING:video_receive_stream.cc(468)] No decodable frame in 3000 ms, requesting keyframe.
[1:48:0507/151923.363879:WARNING:rtp_rtcp_impl.cc(205)] Process: Timeout: No increase in RTCP RR extended highest sequence number.

[1:43:0507/151941.992255:WARNING:packet_buffer.cc(97)] Packet buffer flushed
[1:43:0507/151942.049397:WARNING:rtp_sender.cc(689)] Failed resending RTP packet 12225, Discard rest of packets.
[1:48:0507/151942.257455:ERROR:acm_receiver.cc(49)] AcmReceiver::SetExtraDelay 2198
[1:48:0507/151942.257808:ERROR:channel.cc(1391)] SetMinimumPlayoutDelay() failed to set min playout delay
[1:48:0507/151942.257962:WARNING:channel_proxy.cc(287)] Error setting minimum playout delay.
[1:43:0507/151942.403706:WARNING:rtp_sender.cc(689)] Failed resending RTP packet 12285, Discard rest of packets.
[1:43:0507/151942.417966:WARNING:rtp_sender.cc(689)] Failed resending RTP packet 12290, Discard rest of packets.
[1:43:0507/151942.430505:WARNING:rtp_sender.cc(689)] Failed resending RTP packet 12297, Discard rest of packets.
[1:43:0507/151942.489881:WARNING:rtp_sender.cc(689)] Failed resending RTP packet 12305, Discard rest of packets.
[1:43:0507/151942.497436:WARNING:packet_buffer.cc(97)] Packet buffer flushed
[1:43:0507/151942.515807:WARNING:turnport.cc(456)] Socket is bound to the address:192.168.11.45, rather then an address associated with network:Net[arcbr0:100.115.92.x/30:Unknown].

So it looks very much like network issue at some layer.
I think we can remove the Video component from this bug.
Cc: rajatja@chromium.org kirtia@chromium.org snanda@chromium.org
Components: -Blink>WebRTC>Video
Owner: deadbeef@chromium.org
@sprang, thanks for checking this quickly! I removed Video component.

@deadbeef@ can you please kindly help check if this is something your team can help? Please feel free to reassign if it's not the case.

Also adding WiFi team to help take a look.  

Comment 5 by kirtia@google.com, May 14 2018

@agnescheng, do you need me to check something here?
Hi Kirtika,

When the video chat dropped, WiFi is still connected and workable. However, there are network errors in logs (from https://buganizer.corp.google.com/issues/78315388#comment13). 

One kind DUT show  "Connection lost " ,and we can grep error in file Near Accesspoint_second_test/8/debuglog/var/log/chrome/chrome_20180506-175523:
        [1161:1239:0507/145942.138526:WARNING:name_value_pairs_parser.cc(55)] Key block_devmode already has value (error), ignoring new value: 0
        [1161:1161:0507/145945.558152:ERROR:gaia_screen_handler.cc(593)] Gaia webview error: ERR_INTERNET_DISCONNECTED
        [1161:1161:0507/145945.558317:WARNING:signin_screen_handler.cc(785)] Retry frame load due to reason: frame error
        [1161:1161:0507/145945.558598:WARNING:error_screen.cc(193)] Network error screen message is shown
        [1161:1161:0507/145945.575982:WARNING:CONSOLE(294)] "<webview>: The load has aborted with error -106: ERR_INTERNET_DISCONNECTED.", source: extensions::webViewEvents (294)
        [1161:1161:0507/145950.342342:WARNING:error_screen.cc(203)] Network error screen message is hidden
        [1161:1161:0507/145950.619180:WARNING:CONSOLE(294)] "<webview>: The load has aborted with error -20: ERR_BLOCKED_BY_CLIENT.", source: extensions::webViewEvents (294)
        [1:28:0507/151729.591663:ERROR:stunport.cc(279)] Jingle:Port[0x13a03080:audio:1:0:local:Net[mlan0:192.168.11.x/24:Wifi]]: UDP send of 912 bytes failed with error 1

I am not sure which network layer it might be related. So just loop you in as FYI, if these errors doesn't look like kernel level related, please feel free to ignore. Any suggestion is appreciated. Thanks!

Comment 7 by kirtia@google.com, May 14 2018

Cc: -kirtia@chromium.org kirtika@chromium.org
I think you mean kirtika@.
Labels: Needs-Feedback
I don't have access to the Buganizer bug; can you attach the log to this bug or give me access?

Though from the log messages that have been pasted in comments, it appears that the DUT is being disconnected from the AP and "sendto"s are failing at the OS level.
Labels: -M-66 M-69
Status: Assigned (was: Untriaged)
This bug has an owner, thus, it's been triaged. Changing status to "assigned".
Owner: emadomara@chromium.org
Status: Untriaged (was: Assigned)
Status: Assigned (was: Untriaged)
Cc: jayhlee@chromium.org cvintila@chromium.org
qq: what would be the expected SLA for fixing this P1 issue (logged in May)?
Hello!
This bug is receiving this notice because there has been no acknowledgment of its existence in quite a bit of time
- If you are currently working on this bug, please provide an update.
- If you are currently affected by this bug, please update with your current symptoms and relevant logs.

If there has been no updates provided by EOD Wednesday, 12/19/18 (5pm EST), this bug will be archived and can be re-opened at any time deemed necessary.

Thank you!
Status: Archived (was: Assigned)
Due to lack of action this bug has been Archived. If work is still being done on this issue or you are still experiencing this issue please feel free to re-open with the appropriate information.

Sign in to add a comment