CC crashes at simulate

CC crashes when I hit “simulate”. (Macbook) Any ideas?

1 Like

Send the c2d file to support, there have been a few reports of crashes depending on GPU hardware (I seems to recall)

it happens with any c2d file, but I will send one to support…

I have the same issue with CC Pro 622 on my Mac. Try unchecking High Resolution Simulation under the View tab.

1 Like

Just tried that, it still crashes… Thanks for the tip!

It’s getting annoying. Just lost a design that I forgot to save before simulation… Crash and gone… :confused:

Having same issue with my Mac after updating to the latest version of CC. Regretting that move for sure!

yep, same here. I’ve sent an email about that to support 3 days ago, hope they will have a solution soon…

Still no reply unfortunately on my email to support about the CC crashes. Is it normal that this takes so long?

It’s a holiday in the U.S. — we’re working through tickets as quickly as we can to catch up.

Checking for tickets, I don’t see an open one which matches your name — please write in again — but it may be that it has been transferred into a box which I don’t have access to.

This is the first thing to try to see if the machine is running out of GPU memory. If you’re running CC on an older machine, it’s likely to have less GPU memory than a newer machine.

Mac rendering problems tend to end up in two categories:

  • Older computers without a lot of memory
  • MacOS updates that break OpenGL

We use OpenGL for 3D rendering, which Apple is moving away from, and doesn’t seem to be making any attempt to keep working. We haven’t seen a big jump in reports of rendering trouble recently so I don’t think this is related to a new MacOS update, but that’s something we try to be aware of.

If you have a problem with the 3D rendering, send in the file along with what version of MacOS you’re running and the specs of your Mac so we can look into it and see if it’s likely to be a resource problem.

Finally, for what it’s worth, we develop CC on Mac machines because the compilers are faster so that OS tends to get a disproportionate amount of testing.

3 Likes

I’m using a 3 year old macbook that should be able to do the job. So it’s not an older computer and I do have the latest MacOS version installed. Especially as a beginner, I do need the option to simulate the toolpaths to check what I’m doing. Losing the design because of a CTD is not good. I will try another (windows) laptop instead for the time being but I’m hoping for a fix soon.

Thanks for the reply!

Just started having the same issue on my very old Macbook Pro (after I updated to the latest version of Catalina 10.15.7). I am running CC Pro 530 and any time I try and simulate, it crashes…not even a 3D toolpath…advanced v carve, pocket and contour.

If you manage to get a crash log, please send it in. Maybe that’ll give us a clue about where the problem is.

1 Like

I will send one in this weekend.

1 Like

I am having the same issue here. I have not changed anything on my Mac mini. Now for some reason it’s crashing every time I try to simulate.

Process:               Carbide Create [737]
Path:                  /Applications/Carbide Create.app/Contents/MacOS/Carbide Create
Identifier:            com.carbide3d.Carbide Create
Version:               0
Code Type:             X86-64 (Native)
Parent Process:        ??? [1]
Responsible:           Carbide Create [737]
User ID:               501

Date/Time:             2021-12-03 19:39:56.276 -0700
OS Version:            Mac OS X 10.15.7 (19H1519)
Report Version:        12
Anonymous UUID:        DE270CC3-6A82-8E7B-59BA-B45E80A31734


Time Awake Since Boot: 530 seconds

System Integrity Protection: enabled

Crashed Thread:        0  Dispatch queue: com.apple.main-thread

Exception Type:        EXC_CRASH (SIGABRT)
Exception Codes:       0x0000000000000000, 0x0000000000000000
Exception Note:        EXC_CORPSE_NOTIFY

Application Specific Information:
abort() called

Application Specific Signatures:
Graphics kernel error: 0xfffffffb



External Modification Summary:
  Calls made by other processes targeting this process:
    task_for_pid: 1
    thread_create: 0
    thread_set_state: 0
  Calls made by this process:
    task_for_pid: 0
    thread_create: 0
    thread_set_state: 0
  Calls made by all processes on this machine:
    task_for_pid: 132
    thread_create: 0
    thread_set_state: 0

VM Region Summary:
ReadOnly portion of Libraries: Total=619.1M resident=0K(0%) swapped_out_or_unallocated=619.1M(100%)
Writable regions: Total=667.9M written=0K(0%) resident=0K(0%) swapped_out=0K(0%) unallocated=667.9M(100%)
 
                                VIRTUAL   REGION 
REGION TYPE                        SIZE    COUNT (non-coalesced) 
===========                     =======  ======= 
Accelerate framework               256K        2 
Activity Tracing                   256K        1 
CG backing stores                  336K        2 
CG image                           132K        6 
CoreAnimation                       56K        8 
CoreGraphics                         8K        1 
CoreImage                            8K        2 
CoreUI image data                  572K        8 
Foundation                           4K        1 
Kernel Alloc Once                    8K        1 
MALLOC                           251.1M       84 
MALLOC guard page                   32K        8 
MALLOC_NANO (reserved)           384.0M        1         reserved VM address space (unallocated)
OpenGL GLSL                        256K        3 
STACK GUARD                       56.1M       16 
Stack                             15.6M       16 
VM_ALLOCATE                       15.4M       37 
__DATA                            27.1M      319 
__DATA_CONST                        20K        1 
__FONT_DATA                          4K        1 
__GLSLBUILTINS                    5176K        1 
__LINKEDIT                       393.4M       27 
__OBJC_RO                         32.3M        1 
__OBJC_RW                         1908K        2 
__TEXT                           225.7M      311 
__UNICODE                          564K        1 
mapped file                       51.5M       21 
shared memory                      636K       15 
===========                     =======  ======= 
TOTAL                              1.4G      897 
TOTAL, minus reserved VM space     1.1G      897 

Model: Macmini6,1, BootROM 424.0.0.0.0, 2 processors, Dual-Core Intel Core i5, 2.5 GHz, 4 GB, SMC 2.7f1
Graphics: kHW_IntelHD4000Item, Intel HD Graphics 4000, spdisplays_builtin
Memory Module: BANK 0/DIMM0, 2 GB, DDR3, 1600 MHz, 0x80AD, 0x484D54333235533643465238432D50422020
Memory Module: BANK 1/DIMM0, 2 GB, DDR3, 1600 MHz, 0x80AD, 0x484D54333235533643465238432D50422020
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x10E), Broadcom BCM43xx 1.0 (7.21.190.33 AirPortDriverBrcm4360-1601.1)
Bluetooth: Version 7.0.6f8, 3 services, 27 devices, 1 incoming serial ports
Network Service: Wi-Fi, AirPort, en1
Serial ATA Device: Samsung SSD 860 PRO 256GB, 256.06 GB
USB Device: USB 3.0 Bus
USB Device: Composite Device
USB Device: USB Receiver
USB Device: USB 2.0 Bus
USB Device: Hub
USB Device: Hub
USB Device: IR Receiver
USB Device: BRCM20702 Hub
USB Device: Bluetooth USB Host Controller
USB Device: USB 2.0 Bus
USB Device: Hub
Thunderbolt Bus: Mac mini, Apple Inc., 23.4

I sent crash log and CC file to support for review.

2 Likes

If you google this error, it seems to be affecting quite a few QT-based apps on Macs that run Catalina and have Intel HD4000 GPUs.

Suggestions are that the security update 2021-007 might have broken the Intel graphics driver.

3 Likes

How do I get the crash report on my Mac?

Good catch. I found some more info on it that I’ll try to dig into today. So far it looks like a lot of programs are suffering a similar fate after that Apple update.

3 Likes