Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

The cause of this bug seems to be the OSX system spell checker; I've crashed a few applications to take a look at the dumps, and so far they common point of failure seems to be that they all have some call to something like `NSSpellChecker`.

In the OP for example:

    6   AppKit                              0x00007fff921dbd1a checkDataDetectors + 536
    7   AppKit                              0x00007fff921d9429 NSSpellCheckerCheckString + 13334
    8   AppKit                              0x00007fff921d5f9f -[NSTextCheckingOperation main] + 152

    7   AppKit                              0x00007fff921d9429 NSSpellCheckerCheckString + 13334
This explanation makes sense to me because the spell checker is integrated very tightly into the user-facing text entry experience across the board in OSX. It is one of the few bits of code that could explain reliable failures across applications that we've been seeing.


I've disabled the spell checker a long time ago, but it still happens. So NSSpellCheckCheckString is still being invoked even though the spell check is not running.




Consider applying for YC's Winter 2026 batch! Applications are open till Nov 10

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: