[__NSCFConstantString initialize] may have been in progress in another thread when fork() was called

Written at 2024 Sep 10

51 words

If you upgrade to Mac 14 you may get this when running some program

[__NSCFConstantString initialize] may have been in progress in another thread when fork() was called. We cannot safely call it or ignore it in the fork() child process. Crashing instead. Set a breakpoint on objc_initializeAfterForkError to debug.

https://sealiesoftware.com/blog/archive/2017/6/5/Objective-C_and_fork_in_macOS_1013.html