Monday, 2 September 2013

سمَـَّوُوُحخ ̷̴̐خ ̷̴̐خ ̷̴̐خ امارتخ

Update: See article in the register. Suggests it can be done with as few as 4 characters...

Seriously, if Apple knew 6 months ago, as is being suggested, why was a patch not released. They have an upgrade mechanism.

I can't open my texts until my idiot son sends some new texts to replace the one he sent.

I can tell exactly how many people are using irc on a mac directly and not via irssi on our irc channel.

They better have an update for this damn quick.

Update: Apparently it can be done with 6 characters, three of one, a space and two of another, making 11 bytes in total. I wonder what the bug is.

18 comments:

  1. Just upgrade to ios7 and you won't be affected by سمَـَّوُوُحخ ̷̴̐خ ̷̴̐خ ̷̴̐خ امارتيخ ̷̴̐خ

    ReplyDelete
  2. Replies
    1. Not the name of God or anything, it is the string that crashes every apple device.
      Copy/paste it to something. Very odd that blogspot manages to show it with no crash - may be deliberate.

      Delete
  3. http://www.lifehacker.com.au/2013/09/how-to-crash-ios-or-mac-with-one-string/

    ReplyDelete
  4. Safari 6.0.5 seems to cope with this page until you try to inspect the DOM and show the crasher. Strange.

    ReplyDelete
  5. Stop posting it in IRC. It's a support channel for your company.

    ReplyDelete
  6. LOL, I'm using a Mac, and have opened this page in Chrome, Safari and had it pasted to me on IRC and my OSX 10.7.5 is still rock solid :)

    ReplyDelete
  7. I've seen this page in Chrome, latest Safari and had it pasted to me in IRC on my Macbook Pro running OSX 10.7.5, and it's still rock solid, no crashes :)

    ReplyDelete
  8. Some sod posted it on facebook. I *only just* realized it's not chrome being more crashy than usual.

    Oddly, this blog doesn't crash it.

    ReplyDelete
    Replies
    1. Mea culpa. Post deleted.
      I honestly didn't believe it would really be so simple to crash and burn a browser.

      Delete
  9. Posting it on IRC is.. messy.. But at least I proved it worked :p

    ReplyDelete
  10. Post it everywhere and let it go viral :)

    ReplyDelete
  11. Most things seem unaffected - viewing this page and the page source work fine in Chrome and Safari on OS X, as does pasting the string to the command line (both iTerm and Terminal). "Inspect Element" crashed Safari entirely, but only the element-inspector component of Chrome.

    Irritating, and I do hope it gets fixed ASAP - particularly with the impact it seems to have on iOS.

    ReplyDelete
  12. And now, if I try to view this blog on Safari on iPhone, Safari crashes out...

    ReplyDelete
  13. This post also broke Newsify and Feedly on my iPad - both crashed and Newsify then crashed every time I launched it. I had to switch to my PC to mark this feed as read and reinstall Newsify before I could see any of my other RSS feeds. Very annoying; a very effective DOS attack that took some time to unwind. Chrome and Safari on the iPad both crashed too.

    ReplyDelete
  14. Weirdly enough it doesn't crash on OS X 10.7.5 with Safari 6.0.5. Inspecting the element didn't reproduce either, I suspect it's something to do with specific defective versions of libraries, is anyone who is crashing on OS X 10.8?

    ReplyDelete
  15. So, you're the reason I can't open my entire RSS reader, thanks ;)

    ReplyDelete
  16. But Safari on OSX 10.8.4 is completely happy with it. That's interesting.

    ReplyDelete