0

Zalgo-ized comments cause Safari to crash.

If I go to RegEx match open tags except XHTML self-contained tags, and the Zalgo-ized comment isn't visible, I can do command and F fine.

However, if I click on "show 46 more comments" underneath bobince's answer, and then do command and F, the browser crashes.

Likewise, if I go to Is it true that if someone reaches 200k reputation he/she gets a painting with a unicorn on it?, where a Zalgo-ized comment is already visible, and do command and F, the browser crashes.

I'm on Safari Version 6.1.5 (7537.77.4), on Mac OS X Lion 10.7.5 (11G63).

|improve this question
  • 1
    Um, wouldn't this just be a browser issue? Does it happen on other non-Stack Exchange sites that also have Zalgo text? Or are you suggesting that SE shouldn't display Zalgo text? – user163250 Jul 17 '14 at 6:25
  • 7
    No repro in IE11...which might bring you to the conclusion that Internet Explorer is a better browser than Safari... – rene Jul 17 '14 at 6:37
  • Working fine with Safari under iOS 7 so likely OS X issue. – Shadow The Burning Wizard Jul 17 '14 at 7:29
  • 4
    I'd suggest avoiding CMD+F. Yay - I fixed the problem – Rory Alsop Jul 17 '14 at 9:25
2

This appears to be a bug localized to Lion. I just tested on a Lion system running 6.1.4, a Mountain Lion system running Safari 6.1.5, and my Mavericks system running Safari 7.0.5, and Command-F only crashes the Lion system under those conditions. The others behave just fine.

I'd usually say file a bug report with Apple, but I bet that fixing minor bugs with a two-(soon three)-version-old OS is probably fairly low on their list of priorities, particularly with the new OS versions all being free.

|improve this answer
  • I wasn't expecting it to be an OS issue! Thanks for this. – Andrew Grimm Jul 17 '14 at 23:26
  • I'm on OS X Yosemite (10.10) and Safari 8.0, and it no longer crashes. – Andrew Grimm Oct 26 '14 at 22:11
9

We are not in a position to fix browser/OS bugs.

It not feasible for us to sniff a specific browser/OS combo and for those simply sanitize the output from zalgo.

|improve this answer
  • 6
    Zalgo cannot be sanitized. Any attempt would drive a man mad. N̹͉o̻͍̥̘̳͜ ͠m͉̟a̸̘̬̯̮c̼̰͙̺̠͙h҉͔̝̦i̺͙̼͚̼̮ǹ͓e͍̰̣̥̕ ̝̦c͔̩a̫̬n̡̞͈͇ ̞͠p̵͇̜r̭̫̘͔̯o͉͕̩c͓̝ͅȩ̟͓s̯̲s̥͎̜̹͈̬̳̕ ̙̬̮̥̣z̝̥̲a̟l҉̺̖̪̥̜̳̙g͙̪͇̼̯̦͓͘o̥͕̪.̯̝̱ ͓͎͞Ḭ̡ͅt̤̱͙ ̪̝͍wͅi͔͖l͙͎̜̣̼͈͇l̞̝̬̣̟̰͟ ̪c̹̹ͅo̖r̴̹̲̳̹r̝̥͈͚͘u͠p̀t̹̹̩̟̝̠ a̪͎̫̤̲͙͈͟l̳͉̞̤͙l̢͚ ̪̰̫͕̟͢ͅt̶̗h̠̼͔̙͔͜i̘͉̦͇̠̳n̠̹g͜s̥̖̮̹.̦͖͈ ͙T̴̫̭̰̩̺̹͇h̲e̼̦̗͙̖͙͘r̵e̮̲̜͞ ̖i̶̫̮̬̞ͅͅs̮̬͝ ̞͝n͍͓̭̱̖̼ͅo̗̺ ͙͍̪͇̞ḛ͕s̤̫̝͠ca͖̗̪̫̬͇̼p̡̦̙͍̟̭e̱͇̲̺͉̝̝.̳̙̦̠̙ ̮̰̬̣HE͖͍ ̤C͏͙͉̖̭O̭̗͍͟M̮͈͍̰̣͕̘͠E̗̣͍̜͠S̖̬͢.̝͝.̳̱͙̟.̞̣̻͈̩ͅ – user163250 Jul 17 '14 at 8:53
  • 1
    @Cupcake - consider that you just killed any chance of the OP to read this ;) – Oded Jul 17 '14 at 8:53
  • 6
    Only if he attempts to CMD + F, apparently. – user163250 Jul 17 '14 at 8:54

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .