SIGSEGV crash while removing background

Originator:michal.apanowicz
Number:rdar://FB11744499 Date Originated:Nov 2, 2022 at 11:30 AM
Status:Open Resolved:No
Product:VisionKit Product Version:iOS 16
Classification: Reproducible:No
 
Hi, we are receiving more and more following crash reports from our users. We are not using VisionKit explicitly in our app. According to our investigation, this crash occurs on ViewController where we use WKWebView. We don't have a step-by-step or any way to reproduce this yet. 

BACKGROUND THREAD 9 - CRASHED 
libsystem_platform.dylib. _platform_memmove 
CoreGraphics CGDataProviderCreateWithCopyOfData 
CoreGraphics CGBitmapContextCreateImage 
VisionKitCore -[VKCRemoveBackgroundResult _createCGImageFromBGRAPixelBuffer:cropRect:]
VisionKitCore -[VKCRemoveBackgroundResult createCGImage] 
VisionKitCore __vk_cgImageRemoveBackgroundWithDownsizing_block_invoke 
VisionKitCore -[VKCRemoveBackgroundRequestHandler performRequest:completion:] 
MediaAnalysisServices -[MADService performRequests:onPixelBuffer:withOrientation:andIdentifier:completionHandler:] 
CoreFoundation __invoking___ CoreFoundation -[NSInvocation invoke] 
Foundation __NSXPCCONNECTION_IS_CALLING_OUT_TO_REPLY_BLOCK__ 
Foundation -[NSXPCConnection _decodeAndInvokeReplyBlockWithEvent:sequence:replyInfo:] 
Foundation -[NSXPCConnection _sendInvocation:orArguments:count:methodSignature:selector:withProxy:] 
libxpc.dylib _xpc_connection_reply_callout 
libxpc.dylib _xpc_connection_call_reply_async 
libdispatch.dylib _dispatch_client_callout3 
libdispatch.dylib _dispatch_mach_msg_async_reply_invoke 
libdispatch.dylib _dispatch_lane_serial_drain
libdispatch.dylib _dispatch_lane_invoke 
libdispatch.dylib _dispatch_workloop_worker_thread 
libsystem_pthread.dylib _pthread_wqthread
libsystem_pthread.dylib start_wqthread

Comments


Please note: Reports posted here will not necessarily be seen by Apple. All problems should be submitted at bugreport.apple.com before they are posted here. Please only post information for Radars that you have filed yourself, and please do not include Apple confidential information in your posts. Thank you!