RenderingNG: Ready for the next generation of web content

Re:RenderingNG: Ready for the next generation of web content by bufferoverflow on Friday July 02, 2021 @06:15AM (#27709765)

Seriously, FF on Ubuntu causes 100% CPU usage when watching YouTube in 1080p. Meanwhile Chrome on Windows eats maybe 6-10%.

How is this not #1 priority to fix?

[ Parent | on HN ]

Re:RenderingNG: Ready for the next generation of web content by magicalhippo on Friday July 02, 2021 @07:43AM (#27710224)

Not much FF can do directly AFAIK, since it has to do with the hardware decoding the drivers support.

I've used an addon for a while which fixed it by forcing YouTube to serve h264 rather than vp9 content, as hardware accelerated decoding of h264 worked but not vp9. But lately it hasn't worked well. Haven't investigated if it was due to newer content only being vp9 or if the addon stopped working.

[ Parent | on HN ]

Re:RenderingNG: Ready for the next generation of web content by GrayShade on Friday July 02, 2021 @08:43AM (#27710745)

I think it's a conflict with the sandbox, like it https://bugzilla.mozilla.org/show_bug.cgi?id=1698778.

[ Parent | on HN ]

Re:RenderingNG: Ready for the next generation of web content by muizelaar on Friday July 02, 2021 @09:06AM (#27710992)

I'm pretty sure most users don't have this experience. Can you post a link to a pastebin of your about:support or file a bug?

[ Parent | on HN ]

Re:RenderingNG: Ready for the next generation of web content by TingPing on Friday July 02, 2021 @11:06AM (#27712470)

This is normal. Firefox is only now rolling out accelerated decoding on Linux.

[ Parent | on HN ]

Re:RenderingNG: Ready for the next generation of web content by roca on Friday July 02, 2021 @06:57AM (#27709970)

Comparing across platforms is not a good idea. Different drivers, APIs and platform OS issues dramatically affect these results.

[ Parent | on HN ]