High CPU Usage, Causing Firefox & Firefox Derivatives To Temporarily Stall While Viewing Feed Sections
Summary
Quantum / Gecko rendering engine based browsers stalling and processor temporarily produces a heavy load when encountering a feed "page crease" (ie. when the next section of posts are being rendered). Tested this with several browsers, two separate operating systems (GNU/Linux based with two separate desktop environments and Microsoft Windows 10).
Steps to reproduce
While using Quantum / Gecko rendering engine based browsers (Mozilla Firefox or Firefox derivative), scroll through groups. Monitor CPU fan speed and processor load, as well as monitor browser for temporary stalls.
Platform information
Quantum / Gecko rendering engine based browsers (Goana rendering engine in the case of Pale Moon & New Moon. Goana is a derivative of Gecko).
Tested with:
Linux kernel based environment (openSUSE rolling upgrade edition - x86_64 / KDE Plasma v5.18 - x86_64 & TWM v1.0 - x86_64)
- Mozilla Firefox (v76.0)
- New Moon (Unofficial build of Palemoon - v28.8)
Microsoft Windows 10 based environment (v18362.675 - x86_64)
- Mozilla Firefox (v77.0)
- Comodo IceDragon (v62.0 - based on Mozilla Firefox v65.0)
- Pale Moon (v28.10)
Tested using three devices:
- 4 Core Atom N550 (base frequency: 1.50GHz)
- 2 Core Pentium E5400 (base frequency: 2.70GHz)
- 2 Core i3 370M (base frequency: 2.40GHz)
What is the current bug behavior?
Exponential processors loads when Quantum / Gecko rendering engine based browsers encounter a "page crease" within feeds which can cause the browser to stall. Thus issue is frequently happening while scrolling through groups feeds using Quantum / Gecko based browsers (Mozilla Firefox / Firefox derivative). On further testing, I found that this is infrequently affecting the Newsfeed, as well as affecting Discovery and channels on a even less frequent basis (recommend first examining how this issue is affecting groups).
What is the expected correct behavior?
Scrolling through feeds (encountering "page creases") shouldn't cause processor loads to exponentially increase.
Relevant logs and/or screenshots
The following is an example of scrolling through groups while using Firefox (this example can be considered as being an average worst-case scenario). e927304537698643968b