Yonke imikhiqizo Isithangami Sokwesekwa

So obviously "We’ve reduced CPU usage on macOS in Firefox and WindowServer during event processing" is demonstrably false.

I went to Headspace, streamed an audio in Safari, noted the %CPU in Activity barely budged more than 20%. Then streamed the same audio in Firefox 93, noted the %CPU rocketed up to 150% and the laptop got hot and the fan kicked into high gear. Then I updated Firefox, restarted computer fresh, streamed the same audio and.....surprise, surprise no fix, no change, %CPU rockets up like before.

Recently I upgraded my Windows 10 to Windows 11 and since doing so, I've had consistent errors while browsing the web on Firefox. Most notably the "Humm. We're having trouble finding that site." error message.

For example, when visiting, say Verizon.com, the tab will display the aforementioned error to which I press Try Again and the website loads correctly every-time. No hiccups on the refresh.

I've tried the following:

1. I've performed a completely clean uninstall of Firefox and then reinstall
2. Cleared all browser history/cache
3. Removed all extensions
4. Disabled IPv6, HTTPS Over DNS, No Proxy
5. Ran through Firefox's troubleshooting
6. Used Firefox Troubleshooting Mode in the Browser
7. Tested that the problem does not happen while using Edge

I've never had a single problem on Windows 10 with Firefox. Curious if others are experiencing the same issues and if there are any fixes. Nothing else on the PC has changed.

• Windows 11 21H2 2200.348
• Network driver is the latest Win11 edition
• Firefox 95