Lots of "Failed to get renderer info [0x5 (os/kern) failure]" errors coming to console when I start debugging views in Xcode

I'm working on a pet project and there's one strange issue. When I open Debug View Hierarchy, a lot of similar errors appear in console. It looks like:

2023-06-14 15:47:07.356740+0300 BFB[19678:4582894] [API] Failed to get renderer info (client=0x42b6b2ed) [0x5 (os/kern) failure]
2023-06-14 15:47:07.356807+0300 BFB[19678:4582894] [API] Failed to get renderer info (client=0x42b6b2ed) [0x5 (os/kern) failure]
2023-06-14 15:47:07.359829+0300 BFB[19678:4582894] [API] Failed to get renderer info (client=0x42b6b2ed) [0x5 (os/kern) failure]
2023-06-14 15:47:07.359904+0300 BFB[19678:4582894] [API] Failed to get renderer info (client=0x42b6b2ed) [0x5 (os/kern) failure]
2023-06-14 15:47:07.359964+0300 BFB[19678:4582894] [API] Failed to get renderer info (client=0x42b6b2ed) [0x5 (os/kern) failure]
2023-06-14 15:47:07.363650+0300 BFB[19678:4582894] [API] Failed to get renderer info (client=0x42b6b2ed) [0x5 (os/kern) failure]
2023-06-14 15:47:07.363726+0300 BFB[19678:4582894] [API] Failed to get renderer info (client=0x42b6b2ed) [0x5 (os/kern) failure]

(And so many of them)

What are they caused by and how can I remove this? My pet project is just simple, only standard UIKit items like UIViews / UITableViews are used.

I'm using Apple M2 Max CPU with 32 Gb RAM and Mac OS Ventura 13.4

Swift version is 5.8.1 (swiftlang-5.8.0.124.5 clang-1403.0.22.11.100)

I created another Xcode from scratch, placed simple label and tried to debug its views - errors didn't appear. So may be it somehow related to project... but it doesn't really contain any special.

Thank you.

Up vote post of Alexey_BH Down vote post of Alexey_BH
1.4k views
Posted by
Alexey_BH
Reply
Add a Comment

Replies

I've been seeing the same error, also with an M2 CPU, using Ventura 13.4. I have recently upgraded my system from an older, Intel-based MacBook Pro, and have noticed a few other things didn't work too well after the system migration. Mostly because it was trying to run Intel code through Rosetta in a mostly Apple Silicon toolchain. I needed to install Apple Silicon versions of Java and a number of other tools before things started working correctly. That's obviously not germane to this particular issue, beyond the fact that it has the same kind of smell to me, but I wonder if it might be related to upgrading to Apple Silicon using the migration assistant.

Posted by
a_j_hill
Up vote reply of a_j_hill Down vote reply of a_j_hill
Add a Comment