The experience you described with Firefox 136.0.3 is incredibly frustrating and it highlights an ongoing issue with Firefox’s performance. Having the browser use 140 percent of your CPU even in Safe Mode is not acceptable. These kinds of problems are not just a minor inconvenience, they are a signal that something fundamental needs to change. Hmm weird, I have no problems like you did even on Firefox 136.0.3, my Firefox install is totally fine, but still, I want to spearhead the idea to rebuild Firefox.
This is where a complete rebuild of Firefox with a new engine like Servo could make all the difference. Gecko has served its purpose but it is clear that it is struggling to keep up with modern demands. Servo, being a modern high performance engine, is designed to provide a faster smoother browsing experience while also being more efficient in resource usage. It is exactly what Firefox needs to remain competitive and address the kind of performance issues you and many others are facing.
Mozilla should prioritize investing in Servo and making it the backbone of Firefox. This would not only solve many of the performance problems tied to Gecko but also position Firefox as a true competitor in the browser market. I recently started a discussion advocating for Mozilla to retire Gecko and fully commit to Servo. You can check it out here https://connect.mozilla.org/t5/discussions/when-is-mozilla-gonna-ditch-the-gecko-browser-engine-for-...
We need to push Mozilla to focus on the changes that truly matter. A modern efficient browser engine like Servo could be the solution to the issues you are experiencing and the key to making Firefox great again.
