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

Issue 637370 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Sep 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 1
Type: Bug



Sign in to add a comment

YouTube playback broken on 54.0.2824.0 for Linux only

Project Member Reported by bustamante@chromium.org, Aug 12 2016

Issue description

Version: 54.0.2824.0
OS: Linux - Precise

I'm consistently running into an issue where YouTube videos only play the first few seconds of playback.  And then pause, this happens with Ads as well.

Attached is a net-log from a sample YouTube video, this reproduces on every one I've tried.

What steps will reproduce the problem?
(1) Navigate to https://youtube.com
(2) Open a video for viewing

What is the expected output?

The video should play normally.

What do you see instead?

After a few seconds the video stops playing, and gets stuck buffering (I tested my connection and get 860Mbps down / 660Mbps up so it's unlikely to be a bandwidth issue)

Please use labels and text to provide additional information.

 
net-internals-log (14).json
2.7 MB View Download
Status: Unconfirmed (was: Untriaged)
can you provide a repro url? does it repro only on specific linux hardware?
Sure here's a sample - https://www.youtube.com/watch?v=RoaofsUoHBo

There's also a netlog in the original bug.  I only have the one linux machine, but I can give you details about it:

OS - Ubuntu 14.04 LTS
Processor - Intel® Xeon(R) CPU E5-1650 v2 @ 3.50GHz × 12 
Graphics - Quadro K600/PCIe/SSE2
RAM - 32 GB
Cc: strobe@chromium.org
Does this repro on other versions of Chrome on your machine? For buffering issues you should report feedback within the YouTube page so YT can get accurate logs.
Status: WontFix (was: Unconfirmed)
no response from bug opener. I couldn't repro this issue on Linux + Chrome 54.2832.2. resolve it as won't fix.

Comment 5 by strobe@google.com, Sep 6 2016

FYI, this is usually due to a transient issue with PulseAudio. Try restarting your system.
Yeah, check your syslog for any error messages related to pulse audio. You can manually kill the pulseaudio process and restart it in a terminal to see its output spew too.

We've since this from things like having a symlink in your pulse config directory.

Sign in to add a comment