Hi, I have received lots of crash report recently.The phenomenon is first stuck and then crash.This crash have bothered me for many days.
below is the crash report
In thread 37 I see this:
0 libsystem_kernel.dylib … __psynch_cvwait + 8
1 libsystem_pthread.dylib … _pthread_cond_wait + 1236
2 JavaScriptCore … pas_root_enumerate_for_libmalloc_with_root_after_zone + 192
3 MyApp … MemoryGraph::enumeratHeap(std::__1::function) + 4501704 (MemoryGraphVMHelper.mm:138)
4 MyApp … MemoryGraph::MemoryGraphVMHelper::MemoryGraphVMHelper(bool, unsigned long) + 4502260 (MemoryGraphVMHelper.mm:156)
5 MyApp … MemoryGraph::setup_global_vm_helper(bool, unsigned long) + 4452076 (AWEMemoryGraphUtils.mm:93)
6 MyApp … MemoryGraph::ContextManager::init_suspend_required_info(bool, unsigned long, bool) + 4461860 (AWEMemoryGraphUtils.mm:363)
7 MyApp … +[AWEMemoryGraphGenerator generateMemoryGraphWithRequest:error:degrade:] + 4431676 (AWEMemoryGraphGenerator.mm:164)
8 MyApp … __109-[HMDMemoryGraphGenerator doGenerateMemoryGraphActivateManner:memoryInfo:minRemainingMemoryMB:completeBlock:]_block_invoke + 4321196 (HMDMemoryGraphGenerator.m:551)
9 MyApp … __hmd_safe_dispatch_async_block_invoke + 3137876 (HMDGCD.m:18)
10 MyApp … __DISPATCH_IS_CALLING_block_invoke + 3345820 (HMDCrashAsyncStackTrace.m:175)
11 libdispatch.dylib … _dispatch_call_block_and_release + 32
12 libdispatch.dylib … _dispatch_client_callout + 20
13 libdispatch.dylib … _dispatch_lane_serial_drain + 668
14 libdispatch.dylib … _dispatch_lane_invoke + 392
15 libdispatch.dylib … _dispatch_workloop_worker_thread + 648
16 libsystem_pthread.dylib … _pthread_wqthread + 288
17 libsystem_pthread.dylib … start_wqthread + 8
What is this code doing? And, specifically, how does frame 3 (MemoryGraphVMHelper.mm:138
) call into frame 2?
Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"