given the errors I have seen, I suspect that the time spent generating the preview layer by buffer copying is what is causing a disruption in the data flow. The problem with doing that is that the cost of such operations is "hidden" by being embedded deeply in the Kernel modules which we are not allowed to see. If you want to get an idea how long it takes capture a timestamp before and after you request the image. I have also found that installing the Kernel Debugger will give insights into such behaviors by generating trace ehtries when extended intervals are detected in the kernel

I have similar questions. where do I find documentation on PreviewsAgentExecutorLibrary as the search engine parses compound terms into words and comes up with some really garbaged up search results

I am seeing the same issue since moving up to the latest Xcode and iPadOS levels

we should probably collaborate on this since Apple is not responding to either one of us, I am seeing symptoms that resemble a general reset of the interface due to a fault. I wish I could get an idea of the structure of the bus that the cameras are on. I am also seeing bizarre behavior from the IMU that can only mean that there is some kind of data overrun on the bus due to slow response, Froim my reading of the specs it appears that a ring buffer or MSI is used for status delivery, if the ring buffer wraps or status is not promptly responded to there may be a hardware generated fault on the order of a Machine Checkl. In my former job I was developing PCIe device drivers which sometimes behaved this way

I am having similar message and errors. The error logs presented by Xcode do have eniough information to generate a workaround because they don't identify a Delegate queue specifically nor do they provide enough details to see what is blocking the queues. I have a few feedbacks submitted that describe the errors I am seeing with an extensive trail of logs that are pretty much useless because they do identify which delegate queue is being blocked. I am also getting a message that I am attempting to restart a session that is not stopped which could be at the root of the problem but it does not identify WHICH SESSION is being restarted incorrectly.

[quote='802264022, fbartolom, /thread/759110?answerId=802264022#802264022, /profile/fbartolom'] FigCaptureSourceRemote Fig assert: "err == 0 " at bail (FigCaptureSourceRemote.m:275) - (err=-12784)' I am having similar message and errors. The error logs presented by Xcode do have eniough information to generate a workaround because they don't identify a Delegate queue specifically nor do they provide enough details to see what is blocking the queues. I have a few feedbacks submitted that describe the errors I am seeing with an extensive trail of logs that are pretty much useless because they do identify which delegate queue is being blocked. I am also getting a message that I am attempting to restart a session that is not stopped which could be at the root of the problem but it does not identify WHICH SESSION is being restarted incorrectly. ARSCNCompositor <0x301b84fc0>: ARSCNCompositor (0, 0) initialization failed. Matting is not set up properly. ARDepthSensor <0x301dc1950>: (AVCaptureDeviceTypeBuiltInTimeOfFlightCamera - Back): capture session dropped jasper frame: 334023.383424, LateData ARDepthSensor <0x301dc1950>: (AVCaptureDeviceTypeBuiltInTimeOfFlightCamera - Back): capture session dropped jasper frame: 334023.466850, LateData [/quote] [quote='802264022, fbartolom, /thread/759110?answerId=802264022#802264022, /profile/fbartolom'] FigCaptureSourceRemote Fig assert: "err == 0 " at bail (FigCaptureSourceRemote.m:275) - (err=-12784) ARSCNCompositor <0x301b84fc0>: ARSCNCompositor (0, 0) initialization failed. Matting is not set up properly. ARDepthSensor <0x301dc1950>: (AVCaptureDeviceTypeBuiltInTimeOfFlightCamera - Back): capture session dropped jasper frame: 334023.383424, LateData ARDepthSensor <0x301dc1950>: (AVCaptureDeviceTypeBuiltInTimeOfFlightCamera - Back): capture session dropped jasper frame: 334023.466850, LateData [/quote] I am having similar message and errors. The error logs presented by Xcode do have eniough information to generate a workaround because they don't identify a Delegate queue specifically nor do they provide enough details to see what is blocking the queues. I have a few feedbacks submitted that describe the errors I am seeing with an extensive trail of logs that are pretty much useless because they do identify which delegate queue is being blocked. I am also getting a message that I am attempting to restart a session that is not stopped which could be at the root of the problem but it does not identify WHICH SESSION is being restarted incorrectly.

Interesting that nobody has commented.

thank you

I am seeing the same issue and have been trying since the notices for Mac and iPadOS hit my in box.. I was Abee to pick up the latest Xcode from the distro hub

I am running IOS18.1 Beta 4 but had the problem with previous versions of IOS. I have been getting the errors in _dispatch_assert_queue_fail. No I am NOT modifying the UIVIEW or any buttons during this. The program had been running for several seconds. The error can be pretty much reproduced at will by running for a few seconds I have the back trace from the point of the error if needed. this has been going on since the IOS17 Beta testing.

[quote='789248022, DTS Engineer, /thread/756237?answerId=789248022#789248022'] Try doing less work in a pass or optimize it to help ensure there is a drawable available. A speedier SoC can also process your workload faster. [/quote]

one further question, is there an inventory of active ARSessions in nn ordered list that can be examined?

Actually I tracked it to the initial processing of the Room Capture view class and there are NEW methods that get the errors and they are related to the NSCoder/NSDecoder methhods invoked . I can consitently reproduce the errors using the Out of the Box Room Plan demo from WWDC. I submitted a bug report via the. feedback mechanism from IOS18 Beta 4 after noticing a pattern of behavior stepping the base demo kit through the initiation processing 30+ times where I saw two patterns

Where is the log that I would look at to evaluate the possiblllity of a device or OS issue?

not so harmless at all my metal app won't run properly