I'm also seeing high CPU usage on facebookCoreWWWi.onion (facebook's onion service), so much in fact that it started boiling my stomach from the cpu overheating... I have the latest HTTPS-E (with the fix), and on Linux...
The safest security setting turns off JavaScript, but it also turns off a lot of optimisations. (Because optimisations are fingerprintable.)
Optimisations of JS (i.e. basically JIT) have nothing to do with that since JS itself is entirely blocked, so why am I getting 100% CPU usage in a simple forum on high security setting? (precision: while it's loading up, when the page finally loads up it becomes better)
On the bright side: a FF60-esr based Tor Browser alpha is coming out very soon which will likely not have such a bug. On the darker side: using it will make you more fingerprintable.
The safest security setting turns off JavaScript, but it also turns off a lot of optimisations. (Because optimisations are fingerprintable.)
Optimisations of JS (i.e. basically JIT) have nothing to do with that since JS itself is entirely blocked, so why am I getting 100% CPU usage in a simple forum on high security setting? (precision: while it's loading up, when the page finally loads up it becomes better)
JavaScript isn't the only thing that browsers optimise.
Edit: Browsers optimise parts of the rendering pipelines as well.