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

Issue 648054 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Last visit > 30 days ago
Closed: Sep 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug



Sign in to add a comment

speedy: Video Hangout causes renderer freezes; lots of audio errors in logs

Project Member Reported by derat@chromium.org, Sep 18 2016

Issue description

I just started seeing frequent renderer hangs while in video Hangouts on my personal speedy device, often just a few seconds after starting the Hangout (it was <5 seconds when I repro'd it twice just now). Hangouts is still working on a 52.0.2743.116 samus and a 53.0.2785.103 peppy device.

I started seeing this yesterday with this version:

Google Chrome	52.0.2743.116 (Official Build) (32-bit)
Revision	9115ecad1cae66fd5fe52bd9120af643384fd6f3-refs/branch-heads/2743@{#728}
Platform	8350.68.0 (Official Build) stable-channel veyron_speedy

It's still happening this morning after an upgrade:

Google Chrome	53.0.2785.103 (Official Build) (32-bit)
Revision	303f356b3441ee792fbd8a53a492eb9280c5e9e6-refs/branch-heads/2785@{#845}
Platform	8530.81.0 (Official Build) stable-channel veyron_speedy

I got a hanging-renderer dialog the first time I saw this this morning. I killed the Hangouts/Gmail process but nothing showed up under chrome://crashes. Here's Chrome's user log from the time of the hang:

[742:10575:0918/075902:WARNING:audio_sync_reader.cc(132)] AudioSyncReader::Read timed out, audio glitch count=1
[742:10598:0918/075902:WARNING:audio_sync_reader.cc(132)] AudioSyncReader::Read timed out, audio glitch count=1
[742:10575:0918/075902:WARNING:audio_sync_reader.cc(132)] AudioSyncReader::Read timed out, audio glitch count=2
[742:10598:0918/075902:WARNING:audio_sync_reader.cc(132)] AudioSyncReader::Read timed out, audio glitch count=2
[742:10575:0918/075902:WARNING:audio_sync_reader.cc(132)] AudioSyncReader::Read timed out, audio glitch count=3
[742:10598:0918/075902:WARNING:audio_sync_reader.cc(132)] AudioSyncReader::Read timed out, audio glitch count=3
[742:10598:0918/075902:WARNING:audio_sync_reader.cc(132)] AudioSyncReader::Read timed out, audio glitch count=4
[742:10575:0918/075902:WARNING:audio_sync_reader.cc(132)] AudioSyncReader::Read timed out, audio glitch count=4
[742:10598:0918/075902:WARNING:audio_sync_reader.cc(132)] AudioSyncReader::Read timed out, audio glitch count=5
[742:10575:0918/075902:WARNING:audio_sync_reader.cc(132)] AudioSyncReader::Read timed out, audio glitch count=5
[742:10598:0918/075902:WARNING:audio_sync_reader.cc(132)] AudioSyncReader::Read timed out, audio glitch count=6
[742:10575:0918/075902:WARNING:audio_sync_reader.cc(132)] AudioSyncReader::Read timed out, audio glitch count=6
[742:10598:0918/075902:WARNING:audio_sync_reader.cc(132)] AudioSyncReader::Read timed out, audio glitch count=7
[742:10575:0918/075902:WARNING:audio_sync_reader.cc(132)] AudioSyncReader::Read timed out, audio glitch count=7
[742:742:0918/075902:WARNING:sad_tab_view.cc(111)] Tab Killed: https://mail.google.com/
[742:10598:0918/075902:WARNING:audio_sync_reader.cc(132)] AudioSyncReader::Read timed out, audio glitch count=8
[742:10575:0918/075902:WARNING:audio_sync_reader.cc(132)] AudioSyncReader::Read timed out, audio glitch count=8
[742:10598:0918/075902:WARNING:audio_sync_reader.cc(132)] AudioSyncReader::Read timed out, audio glitch count=9
[742:742:0918/075902:WARNING:sad_tab_view.cc(111)] Tab Killed: https://hangouts.google.com/

The second time, the dialog didn't show up. After 1-2 minutes of Hangouts (and Gmail) being frozen, the Hangouts window briefly switched to fullscreen mode before becoming responsive again and switching to a black screen with white text: "The video call ended because the computer went to sleep." (No, it didn't.)

I see the following in Chrome's user log around the time of the second freeze:

[742:11115:0918/080459:WARNING:audio_input_sync_writer.cc(335)] AISW: No room in socket buffer.
[742:11115:0918/080459:WARNING:audio_input_sync_writer.cc(335)] AISW: No room in socket buffer.
[742:11115:0918/080500:WARNING:audio_input_sync_writer.cc(335)] AISW: No room in socket buffer.
[742:11115:0918/080500:WARNING:audio_input_sync_writer.cc(335)] AISW: No room in socket buffer.

I started a third video Hangout but it hadn't frozen after 10 minutes.

Getting a stack trace when the renderer is killed would be so helpful here. Albert, do you have any ideas about why that isn't happening, or know who might? Also, anyone on the Hangouts side we can loop in?
 

Comment 1 by derat@chromium.org, Sep 18 2016

(I'll submit a feedback report the next time I see this in case the cause could be outside of Chrome.)
Labels: Needs-Feedback
[triage] this could be a symptom of some general performance regression, does this repro on any other web page using lots of CPU? Like HD youtube videos or WebGL games?

Comment 3 by derat@chromium.org, Sep 20 2016

Hmm, I've never noticed it on YouTube on this device. Could a performance regression result in the renderer completely freezing like this? (It's obviously not expected behavior, but I assume that some bug could be triggered when we get too far behind.)

Did we push a minor update to M52 recently before M53 came out? I'm curious about why it suddenly started.
Owner: dgreid@chromium.org
Status: Assigned (was: Untriaged)

Comment 5 by dgreid@chromium.org, Sep 20 2016

Owner: benzh@chromium.org
Ben can you take a look?

IS this speedy only or have we seen it on other devices?

Comment 6 by derat@chromium.org, Sep 20 2016

I've only seen it on this speedy device. It's happened a few times there but I haven't seen it at all on peppy or samus.

Comment 7 by benzh@chromium.org, Sep 21 2016

Haven't been able to repro the hang or the audio errors in #1 yet. I have a DVT2 Speedy with 8530.81.0 test image, doing video hangouts for 10mins.

Comment 8 by derat@chromium.org, Sep 22 2016

I haven't seen this issue again the last two times that I've started a video Hangout from this device. I'm wondering if it could be triggered by server-side behavior or adverse network conditions or something like that (although that still doesn't explain why I didn't see it on the peppy or samus devices).

Is there anything helpful I can do (besides submitting a feedback report) if I see it again?
Status: WontFix (was: Assigned)
No feedback report is the way to go. Since Hangouts is constantly changing their deployed code it's always hard to pinpoint errors like this. Let us know if it happens again.

Comment 10 by derat@chromium.org, Sep 28 2016

Will do. For what it's worth, I've used the same Chromebook for many video Hangouts since the original report and haven't seen this again.

Sign in to add a comment