Macbook Pro crashing after updating to latest Xcode and mac OS. how do i resolve this ?

We don't know which insufficient space it is. How much RAM do you have ? Have you looked at it with Instruments ?

Hi, I have the same problem with Xcode Version 13.3. I will downgrade to older version and will report about it

As per my log simulator is causing issue. Delete the simulator and add it gain

Xcode>window>device and simulators>switch to simulators tab>Select iPhone 13 pro max and delete it> on the bottom click + and add iPhone 13 pro max again.

Try this way . Might work.

As per my log simulator is causing issue. Delete the simulator and add it gain

Xcode>window>device and simulators>switch to simulators tab>Select iPhone 13 pro max and delete it> on the bottom click + and add iPhone 13 pro max again.

Try this way . Might work.

how can I report the bug to apple. I have the same issue. I was hoping that 13.3.1 would be better. unfortunately not. Same error same report?

The same issue

I have the issue when I have the simulator opened.

MacBook 2018 pro Xcode 13.4.1 macOS 12.4

Same issue. Hello Apple. Anyone home? A bunch of your customers seem to have useless, expensive hardware. A hint on how to make it work again would be helpful.

same issue here.

panic(cpu 6 caller 0xffffff7faaee7505): "Submission on work queue 36 failed due to insufficient space!\n" @IGGuC.cpp:2899 Panicked task 0xffffffa51d7ca700: 4 threads: pid 529: SimMetalHost Backtrace (CPU 6), panicked thread: 0xffffffa05119f540, Frame : Return Address

Same issue

`panic(cpu 2 caller 0xffffff7fad8e7505): "Submission on work queue 45 failed due to insufficient space!\n" @IGGuC.cpp:2899
Panicked task 0xffffff8b6f2ec000: 5 threads: pid 628: SimMetalHost
Backtrace (CPU 2), panicked thread: 0xffffff9508a56000, Frame : Return Address`

Same issue using iPhone 13 Pro simulator, happened twice in a day.

Same issue

Same issue. Now it's happening every time I try to run the IOS simulator. I'm using MacOS Monterey 12.4 on a new iMac I bought last year (Intel Core i5). I'm using XCode 13.4.1. I don't get crashes running the same cross platform apps on Android emulator on this same computer. I used to be able to use IOS simulator on this computer with no problems until I updated the operating system and XCode. I'm hoping for a solution besides going back to an older version of XCode because I want to be able to develop for the latest versions of IOS.

Here is a snippet of the crash report: panic(cpu 0 caller 0xffffff7faf0e7505): "Submission on work queue 39 failed due to insufficient space!\n" @IGGuC.cpp:2899 Panicked task 0xffffff869d3743b0: 4 threads: pid 25307: SimMetalHost Backtrace (CPU 0), panicked thread: 0xffffff8b65e1caa0, Frame : Return Address

I have attached a screenshot of the activity monitor shortly before the crash. I can't get a screenshot much closer to the time of the crash because everything freezes.

same issue when simulator or canvas preview inside Xcode is opened.

Same issue

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?