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

jorhelp / Ingram

网络摄像头漏洞扫描工具 | Webcam vulnerability scanning tool

GNU General Public License v3.0

1.73k stars 279 forks source link

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

Closed mistercoder10 closed 6 months ago

mistercoder10 commented 6 months ago

python3 run_ingram.py -i targets.txt -o result

⠿] 0/155(0.0%) Time: 0s/54m 38s objc[29511]: +[NSCFConstantString initialize] may have been in progress in another thread when fork() was called. objc[29511]: +[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.

mistercoder10 commented 6 months ago

Add export OBJC_DISABLE_INITIALIZE_FORK_SAFETY=YES to the .zshrc file should solve this...