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

Issue 711487 link

Starred by 1 user
Status: Untriaged
Owner: ----
Cc:
█ deadbeef@chromium.org
█ emadomara@chromium.org
webrtc-network-bugs@google.com
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Feature



Sign in to add a comment

WebRTC doesn't get any error from Chrome when TCP connections fail

Project Member Reported by deadbeef@chromium.org, Apr 13 2017 
While investigating some logs for failed connections, I noticed this quite often for TCP connections:

[0.057s] Jingle:Conn[...]: Connection closed with error 0

The issue is that pretty much any error information is lost in socket_host_tcp.cc (https://cs.chromium.org/chromium/src/content/browser/renderer_host/p2p/socket_host_tcp.cc), which sends an IPC "OnError" message for every kind of error, with the only argument being the ID of the socket.

It would be useful if more information was passed to the webrtc side, such that it could differentiate kinds of errors (like timeouts vs rejected connection attempts).
Project Member

Comment 1 by sheriffbot@chromium.org, Apr 16 2018

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

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

Comment 2 by anatolid@chromium.org, Aug 6

Labels: -Type-Bug Type-Feature
►

Sign in to add a comment