I use the rendering pipeline urp 12.1.7, and then use the unity2021.3.11f1 version to export the xcode14.2 project, and then run it on the iPhone 11 pro max (16.3), and then click the "M" button to perform gpu capture workload. Once this operation is performed, the memory usage will rise sharply, triggering the out of memory. For example, the memory of the game itself is about 1.3G. Once the gpu capture is performed, it will become more than 2.3G, resulting in the inability to profile the game.
Xcode Graphical Debugger Crash
Posted
by
Share this post
Copied to Clipboard
Reply
I am also having this issue
-
—
smallrainf
-
—
Graphics and Games Engineer
Add a CommentWhen I adjust the newCommandQueueWithMaxCommandBufferCount, it won't appear, but I'm not sure whether it really solves the problem.
How much frames can be in-flight in your application at one time? Is there a limit, like a semaphore, that gets signaled when previous frame finish or something like this? The reason I'm asking is that capture does not pause the application until the whole capture is done. So if the application is pumping out frames and maybe allocating new resources for those new frames, while capture layer still holds on to resources from previous unfinished frames, this can lead to a rise in memory use.