This twit from @glitchr_ crashes the Mac Twitter client, through the Cleansing Fire of Unicrud.

Well done, Sir. Well done.

18 Responses:

  1. Also Chrome, for me. So of course I retweeted it.

    • It didn't hang or crash Chrome for me, but it did strange things to its behavior -- I couldn't add any text to the RT, nor did I have a close button for the tab. However, I could ctrl-W it or backspace to the previous page.

  3. I can view it in a timeline, but trying to view it stand-alone actually manages to sad-tab all of my tabs in Chrome! (I'm guessing it's the unicode in the title element being rendered in the tab list doing it.)

    • Ah, correction: Not all tabs, but it and its neighbors. Powerful stuff! I thought those processes were completely separated.

      • The UI is in its own process.

      • Each site (the details are probably a bit more complicated and have to do with JS somehow) lives in a separate process, so it can happen that several tabs are affected when one goes down.

  4. Had no problem with the OS X client, neither with Chrome.

  6. The tweet in question is U+0488 COMBINING CYRILLIC HUNDRED THOUSANDS SIGN twenty-four times in a row, followed by U+036B COMBINING LATIN SMALL LETTER M and nineteen other combining latin small letters. There's then one space (U+0020) and the whole thing is repeated again twice.

    • I was worried it was the File:/// one...

    • Arnout says:

      It actually starts with U+0647 (ARABIC LETTER HEH). Heh.

  7. Sadly, Twitter don't seem to support OSX any more, so there may never be a fix released.

  8. pavel says:

    I thought the singular was "twat"?

  9. On iOS Twitter client it takes a lot of time to load every single tweet :D Also, on chrome it crashes my closest tabs...

  10. There are horrors lurking in the depths of the Unicode tables no mortal man must know, least their sanity shrivel at nothingness as would grapes, left in the desert sun.

Comments are closed because this post is 13 years old.

  • Previously