Fix the lock order when sending +initialize, so that we don't hold a lock that is meant to protect a runtime data structure while trying to acquire a lock that must be held when running user code that may take an indeterminate amount of time and may trigger deadlocks.
Fix the lock order when sending +initialize, so that we don't hold a lock that
is meant to protect a runtime data structure while trying to acquire a lock
that must be held when running user code that may take an indeterminate amount
of time and may trigger deadlocks.



gnustep/libobjc2,ngrewe/libobjc2,davidchisnall/libobjc2,darlinghq/darling-libobjc2,ngrewe/libobjc2,gnustep/libobjc2,davidchisnall/libobjc2,darlinghq/darling-libobjc2,crystax/android-vendor-libobjc2,crystax/android-vendor-libobjc2