4 ms·
Crash iPhone from Safari (Warning: Direct Link)
- jozan 11y agoVising on that page was a mistake. It made my Chrome on OS X unresponsive for a while (until I force quit) and it polluted my browsing history.
- _kush 11y agoWell, it certainly made my Chrome on OS X unresponsive too.
- jaykru 11y agoAlso did a number on Safari on my Mac (though recoverable of course.)
- dustingetz 11y agoCan you not direct link this please, put it in a text post
- 13of40 11y agoWorks on Chrome too. Not that either one is particularly hard to crash. Too many animated gifs on one page will do it. I rue the day I bought this iPad is what I'm saying.
- darrenkopp 11y agolocks up chrome on windows as well
- trishume 11y agoHow to fix Chrome after clicking: force kill chrome, turn off wifi before restoring tabs, restore tabs, close tab with "no internet" dinosaur, turn wifi back on. Otherwise it will just lock up as soon as you restore your tabs, and you can't close it.
- Benjamin_Dobell 11y agoCrashing a browser isn't particularly difficult. It's whether or not the crash is exploitable that is interesting. Where is the technical description of this crash?
- daigoba66 11y agoWorks as advertised.
- sbdchd 11y agoIf anyone is interested, this is the javascript pulled from the webpage. var total = ""; for (var i = 0; i < 100000; i++) { total = total + i.toString(); history.pushState(0, 0, total); } edit: formatting
- ashertrockman 11y agoApparently this is a known issue: https://code.google.com/p/chromium/issues/detail?id=394296 https://code.google.com/p/chromium/issues/detail?id=394296
- m1k3r420 11y agoLocks up Iceweasel on Debian as well.
- jaykru 11y agoSomething interesting: even having the URL autocomplete from having tried it on my Mac was enough to make my iPhone respring.
- rabboRubble 11y agoDon't recommend opening this link from FF on Windows either!