panic(cpu 2 caller 0xffffff7fb1ae8505): "Submission on work queue 38 failed due to insufficient space!\n" @IGGuC.cpp:2899 Panicked task 0xffffff99d397a350: 5 threads: pid 943: SimMetalHost Backtrace (CPU 2), panicked thread: 0xffffff9509085aa8, Frame : Return Address
Macbook Pro crashing after updating to latest Xcode and mac OS. how do i resolve this ?
Same issue macOS 12.4
Simulator: Version 13.4.1 (977.2), SimulatorKit 618, CoreSimulator 802.6.1
Same issue with me even on most recent update.
Out of curiosity are you guys on Intel Macs or does this also happen for M1, M2's?
Same issue. XCode 13, 14. MacBook Pro (16-inch, 2019) 2.6 / 16. It will soon become 1 year since i first experienced this issue. Reported dozens of crash reports. Apple doesn't care..
Same issue. XCode 13.4.1, simulator iOS 15.5, MacBook Pro (13-inch, 2018, Four Thunderbolt 3 Ports). Crashes are frequent, sometimes even multiple times a day!!!
Same here
MacOSMonterey 12.6.1 (21G217) XCode 14.0 MacBook Pro (Retina, 13-inch, Early 2015) 8GB RAM
Enter debugger: submitToRing: Work queue failure detected
Has anyone found a solution to this issue. I'm really having a hard time working with my device. PLEASE HELP
Same issue. The only solution is not to use iOS simulators, instead using macOS target to run it as a macOS app. (A solution for SwiftUI app) Only in this way, it will not crash.
This issue happens after WWDC 22 and many of you are using previous version of macOS, macOS Monterey, so I guess it's not a bug of the macOS but a bug of Xcode 13.
Same issue its been many many months now with newer Mac OS releases and multiple xcode versions but issue is still not resolved. MBP mid 2019
I just had this start happening within hours of accidentally updating Xcode to 14.2 (14C18) on Mac OS Monterey 12.7 because I tried to run something from the command line. Two kernel panics in 18 hours—and I'm not even using Xcode.
Anyone from Apple actually want to fix this?