I’m seeing a repeatable first-party cameracaptured crash on an iPhone 14 Pro (iPhone15,2) running iOS 27 beta 5 (24A5424a).
The single-camera AVCaptureSession configuration is:
-
Front wide camera
-
3840×2160 at 30 fps, SDR/420f
-
Two AVCaptureVideoDataOutput connections:
- Main recording output: 3840×2160
- Auxiliary preview output: approximately 2096×1178
-
Both connections request and activate .standard video stabilization
Within roughly two minutes, cameracaptured crashed three times—once during recording and twice during idle preview. The application receives AVErrorMediaServicesWereReset (-11819) after each crash.
All three reports have the same faulting queue and underlying stack:
com.apple.coremedia.capture.videodata-stabilization.front
FigCFDictionaryGetCGRectIfPresent -[BWVISNode _transformRectanglesInMetadata:pts:] -[BWVISNode _stabilizeMetadataForSampleBuffer:] -[BWVISNode _tallyAndEmitSampleBuffer:] VideoStabilizationV2
The first two crashes are:
EXC_BAD_ACCESS / EXC_ARM_PAC_FAIL address: 0x00000000dac11a30 termination: PAC_EXCEPTION, code 261
The third reaches the same stabilization stack but terminates with:
EXC_BAD_ACCESS / SIGSEGV KERN_INVALID_ADDRESS at 0x30
App-side frame analytics were disabled, system pressure remained nominal, and neither audiomxd nor bluetoothd restarted. The first crash report also shows two front- stabilization worker threads, consistent with the two stabilized video outputs.
I have filed Feedback Assistant report FB24553011 with the complete log archive and all three cameracaptured reports.
With the iOS 27 public release approaching, waiting for an OS-side fix is not a viable shipping strategy; an app-side workaround is effectively the only option available for our release.
Is this a known issue? In particular:
- Is it safe to leave .standard stabilization on the main recording connection while forcing the auxiliary preview connection to .off?
- Would disabling/removing the auxiliary AVCaptureVideoDataOutput reliably reduce this to one stabilization pipeline?
- If a single stabilized front output remains affected, is disabling front-camera stabilization entirely the only supported containment?
- Is there any public API for disabling the rectangle-metadata processing performed by BWVISNode?
The current field workaround is to use the front camera with stabilization Off, or use a rear camera when stabilization is required.