Pure CSS crashes iPhones affects some browsers
A couple of lines of code that runs in any modern web browser by default may crash Apple's Safari web browser, iPhones and affects select browsers as well.
The code uses the backdrop-filter property and a lot of Div elements (more than 3000) to crash Apple iPhones immediately and freeze certain browsers even on non-iOS systems.
The code was published on GitHub today in readable format and as executable code. I won't link to the demonstration page but you can access the linked resource above and click on the link there to test your browser.
According to the developer, the code will restart iOS 9 and higher devices when webpages that contain it are loaded on the device. Some browsers may freeze or crash as well but I could not verify that.
Safari on Mac OS X devices is affected as well and loading the demo webpage in Safari may require a forced restart and may be the beginning of a vicious cycle as the operating system may open Safari automatically and with it the webpage with the code which in turn may require another restart.
Internet Explorer and Microsoft Edge display notifications that they could not load the webpage while Opera, Google Chrome and Firefox load the webpage just fine.
Reports suggest that some versions of Internet Explorer and Microsoft Edge may be affected as well. Günter Born confirmed that the page crashed Internet Explorer 11 on a Windows 7 system. Neowin suggests that Microsoft Edge, Internet Explorer or Safari may freeze when webpages are loaded.
Other browsers on iOS may certainly affected by this as well as as they are forced to use the same rendering engine.
The developer promises code to crash or freeze Firefox in the coming week. Obviously, there is always the chance that browsers crash when certain code is loaded on webpages. While this should not happen, no browser seems to be exempt from that.
The same developer released a one-liner, JavaScript this time, that freezes Google Chrome and ChromeOS.
There is little that Internet users can do to avoid this issue. CSS instructions are executed on load and may be added to any webpage; this is different from JavaScript which users may block from execution by using programs such as uBlock Origin, uMatrix, or NoScript.
It is up to the browser's developers to fix the issue. While it does lead to freezes or crashes only, it may lead to data loss due to that.
Now You: Is your browser affected by the issue?
Just ran the test on Waterfox 56.2.3 without a crash. OS is Windows 8.1
Something crashes WF intermittently but fairly often on my PC.
@Mike J,
My suggestion would be to create a new profile to test whether the same thing occurs when Waterfox is in a bare bones state i.e. without any prefs changes and no addons.
To create a new profile, open the Run command (Windows key + R) type: “waterfox.exe -p” (without quotes) and hit Enter. When the wizard launches give it a name and then launch Waterfox with the new profile. You don’t have to delete the profile you’re using now.
If a new profile fixes the problem, then it’s either due to an addon or other changes you’ve made in prefs (about:config).
This does not affect Microsoft Edge, as reported on the GitHub page.
Also tested myself and Microsoft Edge didn’t crash.
Edge use different engine from IE
I’m responding to the claim this crashes Microsoft Edge when it doesn’t (has nothing to do with IE).
Microsoft Edge won’t load the page at all, won’t hang nor crash neither (the intent is to crash the browsers).
> Reports suggest that some versions of Internet Explorer and Microsoft Edge may be affected as well.
> Neowin suggests that Microsoft Edge, Internet Explorer or Safari may freeze when webpages are loaded.