WARNING "ASR: No room in socket buffer.: Broken pipe (32)" is reported during meeting and after meeting |
||||
Issue description
(1) Have buddy join meeting where there is other participants.
What went wrong:
from /var/log/chrome/chrome, webrtc logs WARNING "ASR: No room in socket buffer.: Broken pipe (32)".
localhost ~ # cat /etc/lsb-release
CHROMEOS_RELEASE_APPID={B801E98B-4AB6-4D82-B3B3-E1517DC53266}
CHROMEOS_BOARD_APPID={B801E98B-4AB6-4D82-B3B3-E1517DC53266}
CHROMEOS_CANARY_APPID={90F229CE-83E2-4FAF-8479-E368A34938B1}
DEVICETYPE=CHROMEBASE
CHROMEOS_RELEASE_BUILDER_PATH=buddy-release/R64-10176.41.0
GOOGLE_RELEASE=10176.41.0
CHROMEOS_DEVSERVER=
CHROMEOS_RELEASE_BOARD=buddy
CHROMEOS_RELEASE_BUILD_NUMBER=10176
CHROMEOS_RELEASE_BRANCH_NUMBER=41
CHROMEOS_RELEASE_CHROME_MILESTONE=64
CHROMEOS_RELEASE_PATCH_NUMBER=0
CHROMEOS_RELEASE_TRACK=testimage-channel
CHROMEOS_RELEASE_DESCRIPTION=10176.41.0 (Official Build) dev-channel buddy test
CHROMEOS_RELEASE_BUILD_TYPE=Official Build
CHROMEOS_RELEASE_NAME=Chrome OS
CHROMEOS_RELEASE_VERSION=10176.41.0
CHROMEOS_AUSERVER=https://tools.google.com/service/update2
[26484:28399:0112/063510.677962:WARNING:audio_sync_reader.cc(177)] ASR: No room in socket buffer.: Broken pipe (32)
[26484:28414:0112/063555.687559:WARNING:audio_sync_reader.cc(177)] ASR: No room in socket buffer.: Broken pipe (32)
[26484:28485:0112/063955.735635:WARNING:audio_sync_reader.cc(177)] ASR: No room in socket buffer.: Broken pipe (32)
[26484:28520:0112/064155.756229:WARNING:audio_sync_reader.cc(177)] ASR: No room in socket buffer.: Broken pipe (32)
[26484:28528:0112/064225.756302:WARNING:audio_sync_reader.cc(177)] ASR: No room in socket buffer.: Broken pipe (32)
[26484:28540:0112/064310.766152:WARNING:audio_sync_reader.cc(177)] ASR: No room in socket buffer.: Broken pipe (32)
[26484:28574:0112/064425.804727:WARNING:audio_sync_reader.cc(177)] ASR: No room in socket buffer.: Broken pipe (32)
[26484:28622:0112/064710.832665:WARNING:audio_sync_reader.cc(177)] ASR: No room in socket buffer.: Broken pipe (32)
[26484:28666:0112/064910.859573:WARNING:audio_sync_reader.cc(177)] ASR: No room in socket buffer.: Broken pipe (32)
[26484:28710:0112/065140.887301:WARNING:audio_sync_reader.cc(177)] ASR: No room in socket buffer.: Broken pipe (32)
[26484:28732:0112/065255.895590:WARNING:audio_sync_reader.cc(177)] ASR: No room in socket buffer.: Broken pipe (32)
[26484:28848:0112/065655.934763:WARNING:audio_sync_reader.cc(177)] ASR: No room in socket buffer.: Broken pipe (32)
[26484:28926:0112/070110.973906:WARNING:audio_sync_reader.cc(177)] ASR: No room in socket buffer.: Broken pipe (32)
[26484:29012:0112/070541.024517:WARNING:audio_sync_reader.cc(177)] ASR: No room in socket buffer.: Broken pipe (32)
[26484:29048:0112/070756.043804:WARNING:audio_sync_reader.cc(177)] ASR: No room in socket buffer.: Broken pipe (32)
[26484:29109:0112/071126.083286:WARNING:audio_sync_reader.cc(177)] ASR: No room in socket buffer.: Broken pipe (32)
[26484:29142:0112/071241.093403:WARNING:audio_sync_reader.cc(177)] ASR: No room in socket buffer.: Broken pipe (32)
[26484:29215:0112/071656.121677:WARNING:audio_sync_reader.cc(177)] ASR: No room in socket buffer.: Broken pipe (32)
[26484:29231:0112/071741.130935:WARNING:audio_sync_reader.cc(177)] ASR: No room in socket buffer.: Broken pipe (32)
localhost ~ # grep "ASR: No room in socket buffer" /var/log/chrome/chrome | wc -l
803
localhost ~ # grep "ASR: No room in socket buffer" /var/log/chrome/chrome* | wc -l
6081
,
Jan 12 2018
,
Jan 12 2018
This log message isn't supposed to be displayed twice, unless it somehow recovers and then fails again (see https://cs.chromium.org/chromium/src/content/browser/renderer_host/media/audio_sync_reader.cc?l=176). The fact that this message is repeated is consistent with the idea that there are simply too many messages waiting to be read by the renderer (so when the renderer eventually consumes one, we succeed once and then fail again the next time). I guess issue 801327 or issue 801404 is closer to the root cause.
,
Jan 16 2018
,
Jan 17 2018
Hmm. How do you recover from a broken pipe? Are all these new sockets being opened and failing?
,
Jan 17 2018
The "broken pipe" log just means the write failed, for some reason. This reason could be that the buffer is full, in which case it is possible for it to work later if the other end empties the buffer a bit. Calling it "recover" is a bit of a stretch though, since the renderer will probably not manage to ever properly catch up if it got so far behind to begin with.
,
Jan 18 2018
|
||||
►
Sign in to add a comment |
||||
Comment 1 by mzhuo@chromium.org
, Jan 12 20188.4 MB
8.4 MB Download