Page 1 of 1

YouTube fullscreen then back again - high cpu usage

Posted: 2021-04-29, 21:55
by Lunokhod
This is not specific to Pale Moon, more a general You Tube problem, as Chromium did the same, also I tried Pale Moon in Artix with a clean profile, and tried using Devuan (which has quite different OS software versions.) If I hit full screen on You Tube it uses quite a bit of CPU, as the fan speeds up, but when I exit full screen it still carries on using quite a bit of CPU, more than before, also it can hang on full screen for a while and not switch quickly back, and do weird things like fill the browser window for a while and the browser might become unresponsive until it has resolved back to the regular size. It didn't used to be like this.

Re: YouTube fullscreen then back again - high cpu usage

Posted: 2021-04-29, 22:58
by Moonchild
Complain to Youtube. It's pretty telling if it also happens in their preferred web client (Chromium).

Re: YouTube fullscreen then back again - high cpu usage

Posted: 2021-04-29, 23:16
by vannilla
To be fair, sometimes I get high CPU usage even with scripts disabled (by a content blocker) and I'm amazed something like this is even possible.

Re: YouTube fullscreen then back again - high cpu usage

Posted: 2021-04-30, 09:24
by Moonchild
It's perfectly possible to create page code without scripting that fully bogs down any browser.

Re: YouTube fullscreen then back again - high cpu usage

Posted: 2021-04-30, 10:10
by moonbat
The whole problem is the shift of the web from displaying pages with a little dynamic content to full blown applications that don't respect the browser navigation controls, or offer meaningful page titles so that you can easily navigate to them in history. And like applications compiled to binary code, they do their best to mangle, minify and obfuscate their code so that no human can make sense of it unlike how it was before.

Re: YouTube fullscreen then back again - high cpu usage

Posted: 2021-05-04, 13:35
by synthesizer_joe
Yeah this is pretty much the exact same problem I'm having. no solution yet.