How to fix EXC_CRASH (SIGKILL) watchdog termination?-CodePudding

The

Any help in this regard would be much appreciated.

Thanks

CodePudding user response：

Calling closures from notifications async fixes this. You can look at the memory graph to understand this.

CodePudding user response：

Obviously, Thread 0 crashed because it did not get access to the queue used by a NSManagedObjectContext in line 5 with performBlockAndWait. The same queue has apparently also been used in the same thread at other lines with performBlockAndWait (10, 19, 45…). This is no problem, since performBlockAndWait can be called re-entrantly, see the docs.
However, it has apparently also been used by other threads with performBlockAndWait (Thread 9, line 15; Thread 11, line 5). It seems to me that one of these threads allocated some common resource that Thread 0 needs to complete its work - a deadlock.
It is not possible for me to find out what this critical resource is. Deadlocks are often hard to find.
A trivial suggestion that may break you code is to replace a performBlockAndWait by a performBlock and see if the affected thread continues running, even if the code is broken. Maybe this gives you some hint where to look for the problem.