If you had trouble loading websites on Firefox today, you’re not alone. A botched configuration change meant the browser stopped loading web pages, and temporarily hogged CPU resources as it tried to function.
“Earlier today, Firefox became unresponsive due to a change in defaults by a cloud provider which triggered a Firefox HTTP/3 bug. We disabled the configuration change and confirmed this fixed the issue,” Mozilla tweeted today.
The company urged people to restart Firefox, which “should restore normal behavior.”
As 9to5Mac reports, the bug hit Firefox on Linux (Ubuntu), macOS, and Windows, as well as public, Beta, and Nightly builds of the browser. The Firefox iOS app was unaffected because it runs WebKit, like Safari.
Before Firefox released a fix, some industrious web users shared a few workarounds, like disabling HTTP/3 in the browser’s settings or disabling Firefox Data Collection and restarting the browser. With Mozilla rolling out an official fix, however, web users should be in the clear with a simple restart.
