-[AVCaptureSession init] has a watchdog issue in iOS 17

Question

nullluli OP

Created Jun ’24

Replies 1

Boosts 0

Participants 2

My app has encountered many watchdog issues on iOS 17, with stack traces as follows:

Attributed: Call stack 0:
mach_msg2_trap (in libsystem_kernel.dylib) + 7
mach_msg2_internal (in libsystem_kernel.dylib) + 79
mach_msg_overwrite (in libsystem_kernel.dylib) + 435
mach_msg (in libsystem_kernel.dylib) + 23
_dispatch_mach_send_and_wait_for_reply (in libdispatch.dylib) + 543
dispatch_mach_send_with_result_and_wait_for_reply (in libdispatch.dylib) + 59
xpc_connection_send_message_with_reply_sync (in libxpc.dylib) + 263
FigXPCConnectionSendSyncMessageCreatingReply (in CoreMedia) + 291
FigXPCRemoteClientSendSyncMessageCreatingReply (in CoreMedia) + 47
FigCaptureSessionRemoteCreate (in CMCapture) + 131
-[AVCaptureSession _createFigCaptureSession] (in AVFCapture) + 123
-[AVCaptureSession _initWithMediaEnvironment:] (in AVFCapture) + 619
-[AVCaptureSession init] (in AVFCapture) + 415

We also have many iOS 16 users, but have never encountered a watchdog issue with the AVCaptureSession init method in iOS 16. Is there any change in iOS 17 that could have caused this? How can I avoid this issue?

The complete stack trace is attached

avfoundation-watchdog.txt

Boost

Answer 1

Media Engineer OP

Apple

Jun ’24

Are you by chance reacting to the AVCaptureSessionRunTimeErrorNotification and rebuilding your AVCaptureSession from scratch when the error code is AVErrorMediaServicesWereReset? Could be that the crashed daemon hasn't fully respawned. Will you please file a bug report at feedbackassistant.apple.com and include a sysdiagnose?

Thanks.

0