If the app is pre-warm and started, the memory resource is limit and the app exits in background. Does it count as a backgroundExitData.cumulativeMemoryResourceLimitExitCount in Metric Kit?

I receive thousands of metrickit crash reports every day ： EXC_CRASH:<RBSTerminateContext| domain:10 code:0x8BADF00D explanation:process-launch watchdog transgression: application:6559 exhausted real (wall clock) time allowance of 60.00 seconds call stack： 0 libobjc.A.dylib libobjc.A.dylib 1 libobjc.A.dylib libobjc.A.dylib 2 libobjc.A.dylib libobjc.A.dylib 3 libobjc.A.dylib libobjc.A.dylib 4 dyld dyld 5 dyld dyld 6 dyld dyld 7 dyld dyld I have a few questions: 1.Does this mean that the dynamic link is stuck? 2.Where should I fix this problem?