Thanks!

Interesting. I just read this, looked at the "Show live issues" and it was checked. Unchecking it brought back live issues for me!

I filed feedback, no resolution yet.

No performance impact perhaps, but the added debug spam isn't a great thing.

Seeing crashes in a different AppleCV3D function, but in the same device and iOS version.

Nope, still seeing it. I hope all y'all have filed feedback as well.

Reserving memory isn't really possible in iOS. You could review Jetsam reports to see if your app is getting booted. I do wonder how much Room Plan is pushing the device. I recall a developer session from a couple of years ago where the ML guys seemed to hint that ARKit was resource intensive and mixing the two technologies could create a less than responsive experience. But, that was a couple of years ago, maybe things have changed.

Hey @mfstanton. Was this an answer to a different question? P.S., the internal debug output we've been discussing has gotten even more interesting in iPadOS 18.0 beta!