Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(289)

Issue 2639283004: Treat all unexpected socket errors as indicating close. (Closed)

Created:
3 years, 11 months ago by nisse-webrtc
Modified:
3 years, 10 months ago
CC:
webrtc-reviews_webrtc.org, tterriberry_mozilla.com
Target Ref:
refs/heads/master
Project:
webrtc
Visibility:
Public.

Description

Treat all unexpected socket errors as indicating close. BUG=webrtc:7016

Patch Set 1 #

Total comments: 1
Unified diffs Side-by-side diffs Delta from patch set Stats (+7 lines, -11 lines) Patch
M webrtc/base/physicalsocketserver.cc View 1 chunk +7 lines, -11 lines 1 comment Download

Messages

Total messages: 9 (6 generated)
nisse-webrtc
Can you give this cl a try to see it it solves the problem?
3 years, 11 months ago (2017-01-19 13:01:34 UTC) #4
henrika_webrtc
Does not work for me: 01-19 14:31:49.512 13336 13367 W libjingle: (physicalsocketserver.cc:721): Unexpected error from ...
3 years, 11 months ago (2017-01-19 13:32:31 UTC) #5
Taylor Brandstetter
3 years, 10 months ago (2017-02-09 08:59:47 UTC) #9
https://codereview.webrtc.org/2639283004/diff/1/webrtc/base/physicalsocketser...
File webrtc/base/physicalsocketserver.cc (right):

https://codereview.webrtc.org/2639283004/diff/1/webrtc/base/physicalsocketser...
webrtc/base/physicalsocketserver.cc:716: return true;
I don't think this is safe. There are errors besides EWOULDBLOCK on different
platforms that actually are benign blocking errors, in my experience. So the
default should be to assume it's a benign error.

Powered by Google App Engine
This is Rietveld 408576698