High CPU demand from chrome when playing youtube videos below 480p

Sukhoikip

Reputable
Jan 8, 2015
29
0
4,530
First off, relevant specs: i5-4200U CPU, intel HD4400 and Radeon R7 M265 GPUs (latter not involved I think) 8GB RAM, screen resolution 1366x768, Windows 10. Oh and youtube is using the HTML5 player.
As the resolution is what it is, youtube's player sets itself at 480p. Idk if it does this with 1080p screens but I wouldn't know about those.
Starting at the start of January, I noticed some odd behavior with quite a few youtube videos: It would stick on the first frame of a video. It took about a week to find the common thread: they were all uploaded at below 480p, meaning they had to be upscaled. Around the 15th they started playing again, but with much higher CPU usage than >=480p videos. I've tried every video I could and I get the same results. I know the drivers for the iGPU haven't changed at all and GPU-Z tells me that nether GPU is even closed to stressed. I've checked chrome's task manager and found the "GPU process" gets quite ravenous. Though I don't think it should matter, the problem persists on external monitors of the same resolution (there's an old 1280x1024 monitor lying around but laptops don't have DVI outputs).

Does anyone have any idea what changed and/or what to do to fix it?
 
I have basically ditched Chrome for video playback on my Surface Pro 3 (i5 4300u processor, basically the same as your 4200u). I know your have the M265 which might change the story, but on my Surface Pro 3 youtube playback on Chrome decimates the battery, runs the fans at full (really distracting) and often, after a while, starts to thermally throttle and playback becomes choppy. On Edge I can playback 1080P60 videos for hours with only a slight fan hum. I just run a quick check now, a 1080P60 video on Chrome got the CPU to 85 degrees in 2 minutes with HW Monitor reporting 10-17W CPU draw throughout.
Same video in Edge had the CPU under 70 degrees throughout (despite running second on a pre-warmed CPU) with 4-9W on the CPU.

On your system it *might* be trying to leverage your M265 GPU, which could totally change the picture, but whatever's happening, it's obviously not doing it effectively! I haven't looked into this for a while, so the picture may have changed, but when I last looked at this Chrome was defaulting over to their own VP8 (and now VP9) video formats for playback, which few GPUs provide substantial hardware acceleration for. Other browsers (like Edge and Firefox) however will request h264 streams, which GPUs have been able to assist substantially with for years now. Apparently there were (probably still are?) extensions for Chrome which force it to request h264 streams. I just decided to ditch Chrome for video playback (still use it for other things though).

As I say, my info is old now, hopefully someone comes along who has followed these things more closely than I have. But what you describe sounds to me like CPU bottlenecking due to inadequate (or for whatever reason not working) GPU acceleration. You could spend ages trying to figure out why, or just switch to Edge for youtube videos and *quite possibly* (not guaranteed, of course), have no issues whatsoever.