5 ms·
Another reason is that you can recursively define shapes in SVGs and many browsers will happily keep rendering until they run out of memory. WARNING: MIGHT FRE
by 983 9y ago
Another reason is that you can recursively define shapes in SVGs and many browsers will happily keep rendering until they run out of memory.
WARNING: MIGHT FREEZE YOUR BROWSER/OS. CLICK AT YOUR OWN RISK.
https://983.github.io/website/random/slow_1.svg https://983.github.io/website/random/slow_1.svg
- amenod 9y agoBrowser makers still don't seem to understand that they are developing a new OS, where resource management and defending resources from possibly malicious 3rd parties is their core business. It's incredible that we have no way to limit memory and CPU consumption, or that browser doesn't do that automatically. EDIT: interesting, your link made FF sweat, but it didn't stop working when I closed the tab - I had to manually kill the offending process.
- 983 9y agoI fully agree. Imagine my surprise when I was searching the issue trackers for Chromium and Firefox and found that apparently it is fine that SVGs can crash/lock up your browser or even your computer.
- jacobush 9y agoIt took the actual OS makers decades to realise the same thing.
- mmjaa 9y ago.. and just as they were starting to wise up, they decided they wanted to write a browser instead. Insane.