iOS13上的Mapkit MapView VectorKit崩溃

问题描述 投票:1回答:1

随着iOS13的发布,我们正在开发的应用程序上有越来越多的mapKit VectorKit崩溃。我们无法在内部重现崩溃,并且我们自己的崩溃报告者每天收集超过200个崩溃。

根据我们获得的所有信息,当应用程序从后台激活时,崩溃总是发生,并且那时,ViewController视图具有MKMapView子视图。系统渲染地图UI时可能出了点问题。

此问题自iOS11或更早以来似乎是一个持久的iOS问题。现在,与崩溃相关的iOS13系统版本包括13.013.113.1.113.1.2。我已经在Apple Bug报告系统上报告了该问题,但是到目前为止,Apple没有任何响应。

任何建议或提示将不胜感激。

仅供参考。崩溃堆栈如下。

Exception Type:  SIGABRT
Exception Codes: #0 at 0x1a8530ebc
Crashed Thread:  0

Thread 0 Crashed:
0   libsystem_kernel.dylib              __pthread_kill + 8
1   libsystem_c.dylib                   abort + 100
2   libsystem_c.dylib                   __assert_rtn + 204
3   Metal                               MTLIOAccelCommandBufferStorageGrowSegmentList.cold.1 + 0
4   Metal                               MTLReportFailure + 476
5   Metal                               -[MTLTextureDescriptorInternal validateWithDevice:] + 2124
6   AGXMetalA11                         0x00000001a85f93e8 + 64
7   VectorKit                           ggl::MetalResourceManager::newTexture(ggl::Texture const*) + 596
8   VectorKit                           ggl::MetalRenderer::prepareTexture(ggl::MetalResourceManager*, ggl::Texture const*) + 44
9   VectorKit                           ggl::MetalRenderer::_processQueue(ggl::RenderTarget*, ggl::RenderQueue*, id<MTLCommandBuffer>) + 3220
10  VectorKit                           ggl::MetalRenderer::_processQueue(ggl::RenderTarget*, ggl::RenderQueue*, id<MTLCommandBuffer>) + 96
11  VectorKit                           invocation function for block in ggl::MetalRenderer::frame(ggl::RenderTarget*, ggl::RenderQueue*, std::__1::function<void ()>, std::__1::function<void ()>) + 56
12  VectorKit                           invocation function for block in geo::TaskQueue::sync(std::__1::function<void ()>) + 60
13  libdispatch.dylib                   _dispatch_client_callout + 16
14  libdispatch.dylib                   _dispatch_async_and_wait_invoke_and_complete_recurse + 228
15  libdispatch.dylib                   _dispatch_async_and_wait_f + 100
16  VectorKit                           ggl::MetalRenderer::frame(ggl::RenderTarget*, ggl::RenderQueue*, std::__1::function<void ()>, std::__1::function<void ()>) + 544
17  VectorKit                           ggl::RenderFrame::execute(ggl::RenderTarget*, ggl::RenderQueue*, std::__1::function<void ()>, std::__1::function<void ()>) + 120
18  VectorKit                           -[MDDisplayLayer drawToTexture:withRenderQueue:completionHandler:] + 348
19  VectorKit                           -[MetalLayer _onTimerFired:withPresent:] + 280
20  VectorKit                           md::MapEngine::renderScene(double, std::__1::function<void ()>) + 104
21  VectorKit                           md::MapEngine::onRenderTimerFired(double) + 328
22  VectorKit                           ggl::DisplayLink::onTimerFired(double) + 40
23  VectorKit                           -[_GGLDisplayLinkTarget displayLinkFired:] + 84
24  QuartzCore                          CA::Display::DisplayLink::dispatch_items(unsigned long long, unsigned long long, unsigned long long) + 632
25  QuartzCore                          display_timer_callback(__CFMachPort*, void*, long, void*) + 264
26  CoreFoundation                      __CFMachPortPerform + 172
27  CoreFoundation                      __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE1_PERFORM_FUNCTION__ + 56
28  CoreFoundation                      __CFRunLoopDoSource1 + 444
29  CoreFoundation                      __CFRunLoopRun + 2168
30  CoreFoundation                      CFRunLoopRunSpecific + 464
31  GraphicsServices                    GSEventRunModal + 104
32  UIKitCore                           UIApplicationMain + 1936
33  homebrew                            main (main.m:16)
34  libdyld.dylib                       start + 4
ios mapkit mkmapview ios13
1个回答
0
投票

检查您在iOS12和iOS13上的CPU使用率。

[我注意到我的应用程序崩溃是因为我过于频繁地在地图上添加和删除折线(尽管此问题仅在iOS13而不是iOS12中有所体现。

请参阅我关于此here的SO帖子。

查看您的崩溃日志,看看是否发现了这样的内容:

Event:           cpu usage  
Action taken:    Process killed  
CPU:             48 seconds cpu time over 54 seconds (88% cpu average), exceeding limit of 80% cpu over 60 seconds  
CPU limit:       48s  
Limit duration:  60s  
CPU used:        48s  
Duration:        54.45s  
Steps:           15  
© www.soinside.com 2019 - 2024. All rights reserved.