“Crash Safari” Website Crashes Apple’s Web Browser, Also Does a Number on Chrome

9332428567_6c326ffecd_bIf you’ve seen references to a site called crashsafari.com floating around the web, please do us all a favor and not click it or share it, and for the love of Cthulhu please do not use it for a practical joke.

Independent, 9to5MacTelegraph, and a whole host of other sites are reporting that the latest gag to make its way around the internet is a site that exploits the history feature in HTML5 to crash web browsers. It works by consuming more and more RAM until the browser either stops responding, or crashes.

9to5Mac explains in more detail”

The code of the CrashSafari site is very simple. The page includes a header title (which you’ll never actually see because the browser crashes) and a small piece of JavaScript. The JavaScript calls the HTML5 History API thousands of times in a loop, essentially causing Safari to freeze.

The History API is what allows modern websites to change the URL of the page without causing a refresh: scroll 9to5Mac’s homepage and you’ll see the text in the URL bar change. The person behind this site has found that you can cause a crash by abusing the API and calling it thousands of times in quick succession.

You can activate it by browsing to the URL directly as well as clicking on links in apps, like tapping on a link shared over Facebook and Twitter. Depending on how the website is opened, it will either crash the current app, the Safari browser, or the whole of system.

When I tried this on my iPad, the impact was minimal (Safari simply closed), but there are also reports that this gag can crash iPhones. You can see it in action here:

I have also tried this on Chrome on Windows, and I can tell you that this site consumed around 3GB of RAM before Chrome became unresponsive. There’s another report that it’s also causing Android phones to heat up and slow down, but I can’t confirm that (I’m not stupid enough to try the site _again_).

If you’re thinking of playing this joke, don’t. There are funny practical jokes, but this is not one of them.

image by WillzUK

Nate Hoffelder

View posts by Nate Hoffelder
Nate Hoffelder is the founder and editor of The Digital Reader. He has been blogging about indie authors since 2010 while learning new tech skills weekly. He fixes author sites, and shares what he learns on The Digital Reader's blog. In his spare time, he fosters dogs for A Forever Home, a local rescue group.


  1. Mackay Bell25 January, 2016

    Whatever you do, don’t push the big red button.

    1. Nate Hoffelder25 January, 2016

      Is it okay if I push the big green button? (FYI: I’m color blind)

  2. SAD25 January, 2016

    Firefox (Windows desktop version) did OK. It got unresponsive for a moment, then it showed me the usual ‘script is taking too long’ dialog (twice). I clicked ‘stop script’ (both times). It became responsive again, I was able to navigate away from the page.
    It never used more than 1GB of RAM.
    I never thought I would be praising Firefox for stability, of all things.

  3. theboomvoy4 March, 2016

    It works by consuming more and more RAM until the browser either stops responding, or crashes. Where is this information?

    1. Nate Hoffelder4 March, 2016

      I witnessed it myself.

  4. Autymn D. C.11 December, 2019

    Enter “DAISNAID” in the address bar.

    One could turn off Javascript then vet each new site that needs it, but then the allowed sites list can hang the computer.

  5. Autymn D. C.11 December, 2019

    Where’d my comment go?

    1. Nate Hoffelder11 December, 2019

      the moderation queue


Leave a Reply

Your email address will not be published.

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Scroll to top