multiprocessing error when runs on macos big sur

Describe the bug

when sanic starts with multiple session, it crashes as :

objc[96314]: +[__NSCFConstantString initialize] may have been in progress in another thread when fork() was called.
objc[96315]: +[__NSCFConstantString initialize] may have been in progress in another thread when fork() was called.
objc[96314]: +[__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.
objc[96315]: +[__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.

Code snippet app.run( host=“0.0.0.0”, port=port, workers=sessions, register_sys_signals=True, protocol=WebSocketProtocol, )

Expected behavior No exception, no crash

Environment (please complete the following information):

• OS: macos big sur, apple m1
• Version

https://stackoverflow.com/questions/50168647/multiprocessing-causes-python-to-crash-and-gives-an-error-may-have-been-in-progr

[Tronic]

I tried it a couple of years back, specifically to fix this problem in Sanic. Found out that this was the case and then looked it up on Stackoverflow or somewhere that others had noticed the same.

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. If this is incorrect, please respond with an update. Thank you for your contributions.