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 am running crenate levels ant this message started coming out today Could not retrieve MakerNotes dictionary from metadata. Type: Error | Timestamp: 2024-11-22 11:56:44.170049-06:00 | Process: GeoPixel | Library: ARKitCore | Subsystem: com.apple.ARKit | Category: General | TID: 0x6348

0xe00002be. is being delivered in the latest realeased kernel

I am facing the same problem and having issues with restarting the AESESSION. This error is repeatable with every test execution. Where is there a more detailed log for the ARSESSION that will be seen outside of the Xcode execution? ARSession <0x12b068c80>: The delegate of ARSession is retaining 11 ARFrames. The camera will stop delivering camera images if the delegate keeps holding on to too many ARFrames. This could be a threading or memory management issue in the delegate and should be fixed. Type: Error | Timestamp: 2025-02-03 12:01:39.720227-06:00 | Library: ARKitCore | Subsystem: com.apple.ARKit | Category: Session | TID: 0x9224 ARSession <0x12b068c80>: The delegate of ARSession is retaining 12 ARFrames. The camera will stop delivering camera images if the delegate keeps holding on to too many ARFrames. This could be a threading or memory management issue in the delegate and should be fixed. Type: Error | Timestamp: 2025-02-03 12:01:39.791606-06:00 | Library: ARKitCore | Subsystem: com.apple.ARKit | Category: Session | TID: 0x9224 Attempting to enable an already-enabled session. Ignoring... Type: Error | Timestamp: 2025-02-03 12:01:39.947296-06:00 | Library: Recon3D | Subsystem: com.apple.Recon3D | Category: cv3d.recon.sng | TID: 0x63fa ARWorldTrackingTechnique <0x109827480>: World tracking performance is being affected by resource constraints [25] Type: Error | Timestamp: 2025-02-03 12:01:40.055249-06:00 | Library: ARKitCore | Subsystem: com.apple.ARKit | Category: Technique | TID: 0x9036 ARSession <0x12b068c80>: The delegate of ARSession is retaining 11 ARFrames. The camera will stop delivering camera images if the delegate keeps holding on to too many ARFrames. This could be a threading or memory management issue in the delegate and should be fixed. Type: Error | Timestamp: 2025-02-03 12:01:50.583027-06:00 | Library: ARKitCore | Subsystem: com.apple.ARKit | Category: Session | TID: 0x92a5 ARSession <0x12b068c80>: The delegate of ARSession is retaining 12 ARFrames. The camera will stop delivering camera images if the delegate keeps holding on to too many ARFrames. This could be a threading or memory management issue in the delegate and should be fixed. Type: Error | Timestamp: 2025-02-03 12:01:51.683169-06:00 | Library: ARKitCore | Subsystem: com.apple.ARKit | Category: Session | TID: 0x9222 ARWorldTrackingTechnique <0x109827480>: World tracking performance is being affected by resource constraints [25] Type: Error | Timestamp: 2025-02-03 12:01:53.013283-06:00 | Library: ARKitCore | Subsystem: com.apple.ARKit | Category: Technique | TID: 0x92ca ARSession <0x12b068c80>: The delegate of ARSession is retaining 12 ARFrames. The camera will stop delivering camera images if the delegate keeps holding on to too many ARFrames. This could be a threading or memory management issue in the delegate and should be fixed. Type: Error | Timestamp: 2025-02-03 12:01:54.176881-06:00 | Library: ARKitCore | Subsystem: com.apple.ARKit | Category: Session | TID: 0x92d8 ARSession <0x12b068c80>: The delegate of ARSession is retaining 13 ARFrames. The camera will stop delivering camera images if the delegate keeps holding on to too many ARFrames. This could be a threading or memory management issue in the delegate and should be fixed. Type: Error | Timestamp: 2025-02-03 12:01:55.130128-06:00 | Library: ARKitCore | Subsystem: com.apple.ARKit | Category: Session | TID: 0x92ea

There was a release of Xcode 26.2 that was dated December 4th. Then there was a release of Xcode 26.1 on December 16. Which is the most current? Why was there a later release of 26.1 when there was a ralease of that level in November 11 followed by a 26.1.1? This release strategy is somewhat confusing.