4 ms·

This isn't a bug inside WebKit. It's a bug inside Apples CoreText font rendering framework. A `curl https://zhovner.com/tmp/killwebkit.html` https://zhovner.co

This isn't a bug inside WebKit. It's a bug inside Apples CoreText font rendering framework. A `curl https://zhovner.com/tmp/killwebkit.html` https://zhovner.com/tmp/killwebkit.html` in iTerm2 crashes as well. Thread 0 Crashed:: Dispatch queue: com.apple.main-thread 0 libvDSP.dylib 0x00007fff9080ead6 0x7fff907f2000 + 117462 1 com.apple.CoreText 0x00007fff8892cd5c TRun::TRun(TRun const&, CFRange, TRun::SubrangingStyle) + 850 2 com.apple.CoreText 0x00007fff8892c9ee CTGlyphRun::CloneRange(CTRun const*, CFRange, TRun::SubrangingStyle) + 142 3 com.apple.CoreText 0x00007fff8893b764 TLine::SetLevelRange(CFRange, unsigned char, bool) + 162 ⋮ 8 com.googlecode.iterm2 0x000000010003ce63 -[PTYTextView(Private) drawRun:ctx:initialPoint:] + 99 9 com.googlecode.iterm2 0x000000010003d498 -[PTYTextView(Private) _drawRuns:runs:] + 344 ⋮ 41 com.googlecode.iterm2 0x0000000100001bd4 start + 52

deleted 13y ago
[deleted]
ballard 13y ago
Nice. on iOS: Thread 0 name: Dispatch queue: com.apple.main-thread Thread 0: 0 libsystem_kernel.dylib 0x3a315e30 mach_msg_trap + 20 1 libsystem_kernel.dylib 0x3a315fd0 mach_msg + 48 2 CoreFoundation 0x3210c2b6 __CFRunLoopServiceMachPort + 126 3 CoreFoundation 0x3210afd6 __CFRunLoopRun + 814 4 CoreFoundation 0x3207e238 CFRunLoopRunSpecific + 352 5 CoreFoundation 0x3207e0c4 CFRunLoopRunInMode + 100 6 GraphicsServices 0x35c5d336 GSEventRunModal + 70 7 UIKit 0x33f9a2b4 UIApplicationMain + 1116 8 MobileSafari 0x000ff36e 0xf2000 + 54126 9 libdyld.dylib 0x3a25fb1c start + 0 ... Thread 2 name: WebThread Thread 2 Crashed: 0 WebCore 0x382fe95a WebCore::ComplexTextController::adjustGlyphsAndAdvances() + 522 1 WebCore 0x382fb94e WebCore::ComplexTextController::ComplexTextController(WebCore::Font const*, WebCore::TextRun const&, bool, WTF::HashSet<WebCore::SimpleFontData const*, WTF::PtrHash<WebCore::SimpleFontData const*>, WTF::HashTraits<WebCore::SimpleFontData const*> >*, bool) + 318 2 WebCore 0x382fb806 WebCore::ComplexTextController::ComplexTextController(WebCore::Font const*, WebCore::TextRun const&, bool, WTF::HashSet<WebCore::SimpleFontData const*, WTF::PtrHash<WebCore::SimpleFontData const*>, WTF::HashTraits<WebCore::SimpleFontData const*> >*, bool) + 18 3 WebCore 0x382ff990 WebCore::Font::getGlyphsAndAdvancesForComplexText(WebCore::TextRun const&, int, int, WebCore::GlyphBuffer&, WebCore::Font::ForTextEmphasisOrNot) const + 56 4 WebCore 0x382ff862 WebCore::Font::drawComplexText(WebCore::GraphicsContext*, WebCore::TextRun const&, WebCore::FloatPoint const&, int, int) const + 150 5 WebCore 0x3808 PS: I love the C++ namespace 'WTF.' EDIT: complete dump https://gist.github.com/6374524 https://gist.github.com/6374524
- taspeotis 13y ago
  > PS: I love the C++ namespace 'WTF.' I believe that namespace has diagnostic functions that help you answer the question "What's This Function?". So stack trace helpers, and the like.
  - ballard 13y ago
    Template metaprogramming seemed like a good idea initially, but in production it is a horrible construct that should be buried with nuclear waste.
  - Argorak 13y ago
    Thats the "Webkit Template Framework".
  - necenzurat 13y ago
    android has WTF - What a terrible Failure
mmastrac 13y ago
WARNING: the 404 page above is definitely NSFW (likely due to HN adding the backtick to the URL).
- harrytuttle 13y ago
  That's another goatse as far as I'm concerned! Time to scrub my eyeballs...
K0nserv 13y ago
Curling the URL was one of the first things I tried, but I found it actually does work perfectly fine for me.
- Corrado 13y ago
  Yes, I cannot reproduce the crash on OS X 10.8.4 and iTerm2 1.0.0.20130624. Maybe Apple has fixed it in the latest OS patch. UPDATE: It does kill Chrome 31 (individual tab) and Safari 6.0.5 (the whole browser!).
brokenparser 13y ago
It's a bug inside Apples CoreText font rendering framework So that means anywhere the string could appear, the application that has CoreText render the string crashes? Makes me wonder if it'd work by just broadcasting the string as an SSID and wait for someone to look up available networks, or sending text files to bluetooth devices with an Apple mac address. That would be cool, on a bus, in a crowded city, during rush hour.
FredericJ 13y ago
This bug has been reported to Apple already and it's been fixed in Mavericks. I also believe it's been fixed in iOS7 because they did a lot of changes to the text rendering libraries.
blumentopf 13y ago
Starting from which version? CoreText 1.0.4 is not affected.
jamescun 13y ago
I just tried this inside Terminal.app (with a ZSH shell) on 10.8.3 and it just outputs a string, doesn't crash or cause any problems otherwise. http://i.imgur.com/wQ6u8cq.png http://i.imgur.com/wQ6u8cq.png
thousande 13y ago
http://www.paulirish.com/2013/webkit-for-developers/ http://www.paulirish.com/2013/webkit-for-developers/

deleted 13y ago

[deleted]

ballard 13y ago

Nice. on iOS: Thread 0 name: Dispatch queue: com.apple.main-thread Thread 0: 0 libsystem_kernel.dylib 0x3a315e30 mach_msg_trap + 20 1 libsystem_kernel.dylib 0x3a315fd0 mach_msg + 48 2 CoreFoundation 0x3210c2b6 __CFRunLoopServiceMachPort + 126 3 CoreFoundation 0x3210afd6 __CFRunLoopRun + 814 4 CoreFoundation 0x3207e238 CFRunLoopRunSpecific + 352 5 CoreFoundation 0x3207e0c4 CFRunLoopRunInMode + 100 6 GraphicsServices 0x35c5d336 GSEventRunModal + 70 7 UIKit 0x33f9a2b4 UIApplicationMain + 1116 8 MobileSafari 0x000ff36e 0xf2000 + 54126 9 libdyld.dylib 0x3a25fb1c start + 0 ... Thread 2 name: WebThread Thread 2 Crashed: 0 WebCore 0x382fe95a WebCore::ComplexTextController::adjustGlyphsAndAdvances() + 522 1 WebCore 0x382fb94e WebCore::ComplexTextController::ComplexTextController(WebCore::Font const*, WebCore::TextRun const&, bool, WTF::HashSet<WebCore::SimpleFontData const*, WTF::PtrHash<WebCore::SimpleFontData const*>, WTF::HashTraits<WebCore::SimpleFontData const*> >*, bool) + 318 2 WebCore 0x382fb806 WebCore::ComplexTextController::ComplexTextController(WebCore::Font const*, WebCore::TextRun const&, bool, WTF::HashSet<WebCore::SimpleFontData const*, WTF::PtrHash<WebCore::SimpleFontData const*>, WTF::HashTraits<WebCore::SimpleFontData const*> >*, bool) + 18 3 WebCore 0x382ff990 WebCore::Font::getGlyphsAndAdvancesForComplexText(WebCore::TextRun const&, int, int, WebCore::GlyphBuffer&, WebCore::Font::ForTextEmphasisOrNot) const + 56 4 WebCore 0x382ff862 WebCore::Font::drawComplexText(WebCore::GraphicsContext*, WebCore::TextRun const&, WebCore::FloatPoint const&, int, int) const + 150 5 WebCore 0x3808 PS: I love the C++ namespace 'WTF.' EDIT: complete dump https://gist.github.com/6374524 https://gist.github.com/6374524

taspeotis 13y ago
> PS: I love the C++ namespace 'WTF.' I believe that namespace has diagnostic functions that help you answer the question "What's This Function?". So stack trace helpers, and the like.
- ballard 13y ago
  Template metaprogramming seemed like a good idea initially, but in production it is a horrible construct that should be buried with nuclear waste.
- Argorak 13y ago
  Thats the "Webkit Template Framework".
- necenzurat 13y ago
  android has WTF - What a terrible Failure

mmastrac 13y ago

WARNING: the 404 page above is definitely NSFW (likely due to HN adding the backtick to the URL).

harrytuttle 13y ago
That's another goatse as far as I'm concerned! Time to scrub my eyeballs...

K0nserv 13y ago

Curling the URL was one of the first things I tried, but I found it actually does work perfectly fine for me.

Corrado 13y ago
Yes, I cannot reproduce the crash on OS X 10.8.4 and iTerm2 1.0.0.20130624. Maybe Apple has fixed it in the latest OS patch. UPDATE: It does kill Chrome 31 (individual tab) and Safari 6.0.5 (the whole browser!).

brokenparser 13y ago

It's a bug inside Apples CoreText font rendering framework So that means anywhere the string could appear, the application that has CoreText render the string crashes? Makes me wonder if it'd work by just broadcasting the string as an SSID and wait for someone to look up available networks, or sending text files to bluetooth devices with an Apple mac address. That would be cool, on a bus, in a crowded city, during rush hour.

FredericJ 13y ago

This bug has been reported to Apple already and it's been fixed in Mavericks. I also believe it's been fixed in iOS7 because they did a lot of changes to the text rendering libraries.

blumentopf 13y ago

Starting from which version? CoreText 1.0.4 is not affected.

jamescun 13y ago

I just tried this inside Terminal.app (with a ZSH shell) on 10.8.3 and it just outputs a string, doesn't crash or cause any problems otherwise. http://i.imgur.com/wQ6u8cq.png http://i.imgur.com/wQ6u8cq.png

thousande 13y ago

http://www.paulirish.com/2013/webkit-for-developers/ http://www.paulirish.com/2013/webkit-for-developers/