Hi Alex,
Using FF 45.9 here, but what you are seeing is somewhat similar to what I've seen with FF. I've attached what the current 'steady state' CPU load looks like on my machine (5-core). This is with about 5 browser windows open and normal assortment of sites loaded: news, hobby interests, OS/2 World forum, etc.
In short, you can see load that's balanced across the multiple cores, else if I throttle down to a single core I get a 100% utilization.
Now, this is not exactly that same as what you are seeing, but to Dave's point, the combination of JS and image properties cause a known issue with our browsers.
Specifically, as we were building up to the official release of FF 45.9 these are some of the notable disocveries raised:
1) SET NSPR_OS2_NO_HIRES_TIMER=1
- I have the above setting in my CONFIG.SYS, anything else causes a steady 100% spike across multiple cores
2) layout.frame_rate
- general choppiness of the browser response, you have some control over this, need to play around with a few different rates
- I have my set to the default value of '0', anything else just did not work here well enough
- good description of this can be found
https://github.com/bitwiseworks/mozilla-os2/issues/208 and
https://github.com/bitwiseworks/mozilla-os2/issues/2203) add-ons???
- few are known to be resource hungry, I have disabled Chatzilla here, I think others have experienced problems with it as well?
[EDIT]
Ahh, as I did the preview of my post I noticed you found your fix...well, going to leave my response in-place since I spent the time typing this stuff up and re-freshing my memory on the FF specific tickets.
