-
-
Notifications
You must be signed in to change notification settings - Fork 285
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
+[__NSCFConstantString initialize] may have been in progress in another thread when fork() was called. #542
Comments
I'm seeing the same issue on MacOS 12.4 I am not using Twilio. I have had this issue on MacOS since 2020 personally and was never able to use django-rq for my local development environment. |
@poitch can you try to reproduce this locally and send a few stack traces? Also, does Django RQ's test suite runs on your local development environment? |
This issue may be related to #375 @poitch @Ebrahimhammad . Have you tried changing the worker class to |
Had the same problem on M1 mac. Fix: Set an env var in your terminal. Description: rails/rails#38560 (comment) |
I have the same issue as the OP on my M1 Mac. I tried to using RQ = {"WORKER_CLASS": "rq.SimpleWorker"} That prevented the error from happening. Running the worker with |
when trying to start a delayed shared_task from a management command by another terminal process |
Hi all,
issue is below:
objc[8104]: +[__NSCFConstantString initialize] may have been in progress in another thread when fork() was called.
objc[8104]: +[__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.
14:35:46 Moving job to FailedJobRegistry (work-horse terminated unexpectedly; waitpid returned 6)
After a little research, it seems specifically related to macOS. I am using it on production on Ubuntu server and it is working fine.
But on my local machine, macOS, this error showing up.
.. now this error is showing when I am trying to send a message through Twilio.
I am not sure now if this caused by Twilio or Django-rq ?
Thank you
The text was updated successfully, but these errors were encountered: