I’ve not found a repeatable recipe yet, but it has happened to me a dozen or so times now.
While working on a design, the UI gets stuck and no longer responds to inputs, but the “file” menu still works, so at least I can save, exit CC and then load it back later.
It tends to happen when I’m trying to move design elements (like texts or circles) around in the Design view, but it is not repeatable at all.
Any ideas on how to help debug this/making it more repeatable?
closest to a repro case I have come up with
- load the attached file
- go to the toolpath screen and use “Show Simulation” – keep the simulation active
- go to the Design screen
- move the circles around a bunch of times
- after a couple of times (usually less than 10) of picking a circle and dragging it around, the GUI gets stuck
pawtest2.c2d (748 KB)
I tried to duplicate this, but couldn’t on Windows 11.
Are you having this happen on Windows 10 or Mac OS? Which specific build/version?
Windows 11 Home (22H2, build 22621.1413)
Not entirely surprised you can’t repro; it has been very slippery to repro but the process above I have done 4 times now and each time it got stuck within a minute or so of dragging the smaller circles around.
Edit: it seems step 2 is not needed for this; I just load the file, select a circle at the bottom, and move it around quickly. sometimes the first time I do this hangs, sometimes I go to the second circle after some 10 seconds, and the same quick drag around causes it
I dragged a bunch of times with no problem in Windows 11 — do you have a Windows 11 machine to test?
We’ll see if we can find someone with that Windows build (my own Windows 10 machine is still back on 1703)
I just tried on another computer with Windows 10 and it does not repro there.
running in windbg I get it to print “D3D11: Removing Device.” basically about the time of the freeze,
and then – and only on this getting stuck – do I get a crash deep in QT5 when I close the app… not too useful I suspect
(the D3D11 Removing Device I reproduced twice now so that seems to be a signal and googling that message indicates that 1) something went wrong and 2) a gui hang is then expected)
fwiw system in question is 11th gen Intel with Intel graphics
(if it’s a graphics driver thing I might need to go yell at people at work I suppose)
Can you capture a video of the problem? I can’t make it happen on a Surface Pro, but it figures that Intel and Microsoft would collude to give the Surface “The Best Video Drivers”. (Note: Arjan is at Intel, so this is purely a nerd joke)
Jokes aside, what brand of PC are you using? I’m not sure the video driver would matter, since the Qt canvas should be software rendered, but we’ve been burned bad by Dell drivers before and that D3D message is interesting.
I’ll grab a video tomorrow
and yes it’s a dell
It’s always a Dell. Years ago, we actually had a Dell engineer that happened to own a Shapeoko get in touch and tell us that they commonly have outdated drivers. Sure enough, Dell updated months later and all of our troubles went away. Weeks and weeks of debugging wasted on a Dell problem.
If your machine also has a dedicated GPU, can you pin CC to the Nvidia/ATI GPU and try again?
FYI: I am unable to reproduce on a Thinkpad running Win10.
Video at Carbide Create D3D11 GUI hang - YouTube (once youtube finishes “processing” it)
I grabbed the latest graphics driver from
and now I can no longer reproduce this… So yeah this looks like a driver issue somehow. Sorry for the noise… hopefully if someone else hits this issue this helps them solve it as well
1 Like
That’s actually very helpful. We’ve seen this from a couple of folks, but we’d never seen it as a driver issue before.
hmm one more thing I’m noticing; it seems the “it gets stuck” (almost) always happens at a place where a “snap point” (center or the 4 wind directios) of the circle is at some other snap point in the design… as if that is where the offending thing goes to the graphics driver
the video (which youtube finally processed) shows a clear example of that
It would be interesting to see if that happens even if you make the grid bigger. It could be that you’re almost always at a snap point when it’s a smaller grid relative to the zoom level.
I am having the same problem. - windows 11 latest beta tried and still UI locks up. Anyone figure anything out?
for me it went away once I updated my graphics driver
2 Likes
I increased the memory to 16 GB on a new HP Victus Gaming laptop and have not had a problem since. For some reason, Carbide Create eats excessive memory on newer devices with 11. I run Create on 2 other computers using 10 and 11 with 16 GB and have never had a problem. You can check in Windows “Task Manager” to check the memory consumption of the program.
I had the same problem with the previous version. CC inhale my computer’s memory ang got stuck. My solution was to increase the memory to 16 GB, and even though some times eats up to 12GB. I think is a problem on how CC interacts with windows regarding the removal of the non used pages of the program located in the computer memory.
A memory leak in a graphics driver seems more likely.
Please post a step-by-step set of instructions for making a file which causes Carbide Create to use a large amount of memory and we can have a couple of folks repeat them and post their memory usages.
This topic was automatically closed after 30 days. New replies are no longer allowed.