Under the heading of: I'm not really sure? Maybe some developer[s] will say I am blowing smoke?
Thinking here that perhaps someone new in development, perhaps a contractor from overseas, may not understand the concept of event loops. Last time I debugged this it turned out 'he' had created multiple event loops with arbitrary jumps between one event loop and another. Some library may be damaged? Two crashes?
I don't know.
Application Specific Information:
BUG IN CLIENT OF LIBPLATFORM: os_unfair_lock is corrupt, or owner thread exited without unlocking
Abort Cause 35334
From the developers' forum back in ancient pre-SWIFT times.
The problem is resolved by switching to posix_spawn(). I stil haven't tested that on 10.6-10.11 yet though. My GCD version didn't work on older OS versions. My NSTask version started failing in 10.11 and didn't work at all in 10.12. That's why I switched to fork() to begin with. One out of 4 APIs is functional.
There is also this:
https://stackoverflow.com/questions/72573424/error-libsystem-platform-dylib-os-unfair-lock-corruption-abort-during-saving-da