• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Chrome in Windows 10: Bad performance.

Derpp

Junior Member
Hey everyone, I installed windows 10 yesterday, and I have noticed that video playback on Chrome (youtube 1080p fullscreen) has become incredibly choppy. There's some very noticeable frame rate lag. Is anyone else experiencing this or is it just me?

I have tried turning off hardware acceleration, and it doesn't fix the choppyness.

And oddly enough, Microsoft Edge has buttery smooth video playback.

Testing rig is a Lenovo Yoga 2 Pro, i7 4510U with HD4400 graphics.

So yeah, is anyone else experiencing this?
 
How does Firefox run? And how Firefox runs when you disable flash (Ctrl-Shift-A)? I watch videos at 360p, and usually download them for even better smoothness.
 
I managed to fix most of the framerate lag by getting a chrome extension that forces h.264 encoding (h264ify) on Youtube. However, it's still not as buttery smooth as Edge.

As for how firefox performs, I'm not sure. I don't have it installed.

Another thing I noticed is that Chrome has far more CPU usage when watching HD youtube compared to Edge. Chrome is making temps hit high 70's, whereas Edge is barely hitting 70!

Chrome is just not being nice to the Yoga 2 Pro running Windows 10. I'm actually seriously considering switching to Edge as soon as it gets extension support, unless Google fixes Chrome.
 
Go to chrome://gpu and see if hardware acceleration is enabled. If it's not go to chrome:flags and enable "Override software rendering list" and possibly "Enable GPU rasterization."
 
Both hardware acceleration and rasterization were already on. h.264ify seems to have fixed most of the major framerate issues, but there's still some microstutters here and there. Possibly due to my cpu throttling from hitting 80 degrees from just watching 1080p60fps on youtube.

Edge has none of these framerate issues, and it barely hits 70 degrees.

So it seems like chrome just happens to use an abnormally large amount of cpu power for video playback on my Lenovo.

Also of note, chrome on my main rig running windows 7 doesn't have these issues. And my Lenovo previously on 8.1 didn't have these issues either.

So it seems to be a Windows 10 and Chrome conflict?
 
Last edited:
I clean installed W10 and everything is fine except that both in Chrome and Firefox when I'm on facebook the chat message sound wont work and this does not happen in Edge or IE. Anyone with this also? Other things like webradio or youtube work.

Also this happens -
 
Last edited:
Nope, I don't have that. Facebook works fine for me.

One other thing of note. Edge starts up almost instantly, whereas chrome takes a solid 3 seconds to start up and load google. Although, chrome has always been a bit slow on the startup on my Yoga 2 pro.
 
Probably due to Win10 video driver immaturity. will most likely work itself our over the coming weeks/months as drivers improve.

Right click the youtube video and select "Stats for Nerd" to check which encode is being used in the mime type. Possibly they are using different encodes.
 
Just an FYI. After I installed 10 on my Dell venue 11, I hade sound and screen brightness adjustment issues. I ran windows update and there was a few updates relating to video and sound. Once those installed all worked great.
 
It has to be audio issues but in Edge that notification sound works so... is there something missing from chrome and ff? note that not everyone seems to have this issue...
 
If I had to guess, I'd say the current version of Chrome is not utilizing your video card correctly with Windows 10 drivers. May have to just give it time. Or give FF a try. Been playing videos in Firefox for months on preview builds with no issues.
 
If I had to guess, I'd say the current version of Chrome is not utilizing your video card correctly with Windows 10 drivers. May have to just give it time. Or give FF a try. Been playing videos in Firefox for months on preview builds with no issues.

I've tried both (Chrome and FF) and they reproduce videos as it should but it's that little annoyance on Facebook (and Messenger, the dedicated chat webpage of Facebook) of not reproducing sound on notifications, unlike Edge which does.

I'm enjoying the new browser but still needs work, Firefox isn't in my Win10 as sharp as it was on Win7.
 
What does chrome://gpu show as being accelerated? Everything except rasterization should be hardware accelerated by default unless some driver/hardware compatibility prevents it from doing so (it will give the reason).
 
Everything except for rasterization is being hardware accelerated.

I assume the issue is just a combination of driver immaturity in Windows 10, and bad gpu utilization in Chrome.

The fact that my display is 3200 x 1800 could be another factor as well. The driver might not be that optimized for it.
 
Everything except for rasterization is being hardware accelerated.

I assume the issue is just a combination of driver immaturity in Windows 10, and bad gpu utilization in Chrome.

The fact that my display is 3200 x 1800 could be another factor as well. The driver might not be that optimized for it.

What happens when you launch it with the --disable-gpu option?
 
What happens when you launch it with the --disable-gpu option?

As in launching chrome with hardware acceleration off? Everything is basically the same. Launch speed is the same, although there seems to be higher CPU usage.
 
I've never tried Edge, but if it's better than IE and already works well in Windows 10, it does sound like installing the Chrome Malware is just a waste of space.

Chrome is the best browser unless edge soon proves otherwise. Your link is from 2012. btw. And I may or may not have worked for avast at one point. It was a bad avast update. LONG LONG gone. 3.5 years
 
Back
Top