-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cura 4.7 and 4.7.1 crash at preview for large model #8444
Comments
...So this took about 3.5 hours to slice. In my case the resulting file size is 248MB. It was able to load the preview fine using my RTX 2070 GPU: The resulting g-code contains 6987764 I suggest you switch to compatibility view. It doesn't look as fancy, but it also doesn't use nearly as much VRAM. It's an option in the preferences. Working to the limits of the VRAM capabilities of the GPU is out of scope for us at the moment. The compatibility mode will have to do. |
The GTX 1080 Ti has 11GB VRAM. Not sure where the 6GB VRAM value came from, but it's not correct. Maybe you looked at the 980 Ti specs? |
Ah, yeah I took it from here but you're right, I looked in the wrong column. |
Does it help to set layer view to compatibility mode? Maybe a dxdiag report would help to debug what happened. It could still be memory limits if you are running other applications that also stay in VRAM. |
DxDiag info: https://drive.google.com/file/d/1Uiy--tVVU698CbIGuVtElRpjAXxgFb_O/view?usp=sharing |
OK, slicing finished. Same crash. Maximum GPU VRAM usage was 4717 MB right before the crash, with compatibility setting enabled. Cura processes the preview right up to 99%, sits there for a few seconds, Cura DRAM usage (computer memory) spikes to values around 8.5 to 9 GB while layer preview is generated, and then the crash happens. Here is a screenshot of GPU values as well as DRAM values during slicing: http://gpuz.techpowerup.com/20/09/29/jhh.png Maximum System memory usage was 18449 MB at the time of the crash, out of 32 GB available. |
This is the relevant part of that DxDiag:
This error code |
Very interesting. I guess I'll have to switch to 64 GB RAM soon 😄 |
Application version
4.7.0, 4.7.1, possibly earlier.
Platform
Windows 10 x64 1909
2x GTX 1080 Ti in SLI
CPU: Intel i7 6800K
RAM 32GB DDR4 @3000 MHz
Printer
Creality CR 10 MAX
Reproduction steps
I have been commissioned to print a large model. This is the model and it needed to be resized such as the largest size should be 420mm.
After resizing and arranging the model on the plate like a litophane, I started slicing. Sometimes Cura would not slice at all immediately saying `"Unable to slice", after moving the model back and forth by 1mm on the plate I try again and eventually it starts slicing, which takes a while.
After it finishes, I can't preview the model. Cura crashes every time I try doing that. Below you can read the relevant log.
Interestingly, I get a warning saying `"Mesh has overlapping faces!" - I checked with various tools (Netfabb, meshMixer) and the model is manifold. At any rate, when I try to preview the sliced G-Code (it's 1.05 GB in size), Cura memory usage jumps to around 8-9 GB, fluctuates there and crashes. Logs show no crash reason, but I assume there is a memory overflow exception somewhere triggered by this large and complex model.
With Cura being the only slicer reliably using Tree Supports, and this being a complex model which doesn't really work otherwise, I am stuck.
FYI I have successfully sliced and previewed the model at 100% scale and printed it with no issues.
Project file
The generated GCode is 1.05 GB large. Here are the steps to reproduce:
Download this model:
https://www.myminifactory.com/object/3d-print-alexander-and-diogenes-133982
Rotate the model on the plate in such a way that the baso-relief stands upright.
Resize model in Cura to Z=420 (all other dymensions synchronized)
Enable Tree Supports
Slice the model.
Log file
The text was updated successfully, but these errors were encountered: