[vegardx]

This is amazing! Finally I'm able to watch YouTube without my Macbook initiating a take off sequence when something is available in resolutions over 1080p.

On OSX there is a noticeable difference in performance of video playback in Safari and Chrome, and I'm pretty sure it's all down to hardware accelerated decoding.

[jaxbot]

Yep, see this: https://code.google.com/p/chromium/issues/detail?can=2&start...

They've got hardware accelerated CSS3 working right in the latest versions, but VP8/VP9 won't work. The explanation is that Safari doesn't support VP8/VP9, so a fallback to h264 happens and the hardware accelerates that properly.

[vegardx]

I've noticed hardware accelerated CSS3, much to my despair, as it triggers the discrete gpu. It makes everything freeze for a split second, draw the page, then switch back to the integrated gpu, again with a slight freeze. And if I'm really lucky, the whole process of switching gpus will just crash resulting in a forced reboot.

But I can't really blame Chrome for something that is out of their control. I recommend checking out gfx.io, that way you know what gpu is active. You can also lock it to internal only if you don't use external displays or anything that really requires the discrete gpu.

[simoncion]

These crashes are happening on a Linux machine, rather than a Mac or one running Windows, right?

[vegardx]

I'm running a Mac, but I have a hunch that it might be related to a hardware bug which prompted Apple to extend the warranty of my laptop.

[simoncion]

That sucks. Any chance Apple will trade you for a non-defective model?