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
'Cannot allocate memory' when exporting mesh #259
Comments
What's the export chord tolerance? You could genuinely have a mesh larger than ~3GB. |
0.01mm. Looks like 0.1mm works. However, a previous version of this model exported just fine at 0.01mm and resulted in an STL file of only about 140 KiB. The only difference between the versions are slightly changed constraints. EDIT: Also, setting the render chord tolerance to 0.01mm still works. |
Render chord tolerance is in % not mm. |
But the calculated value in mm is displayed next to the value in %, no? Setting the percentage such that this value is 0.01mm still works (which incidentally is 0.01%). Even with 0.005% it still renders fine (and displays a rounded tolerance of 0.00mm). I also get the feeling that the GUI is a bit borked since the displayed values are sometimes not updated and sometimes change when I change nothing, so it's a bit hard to tell what the actual values are. |
@whitequark, @jonas-schievink fixed here |
@Evil-Spirit Can you check if this addresses any of our other issues where mesh generation is slow? |
@whitequark ofc |
@Evil-Spirit Thanks! Fixed in master. |
System information
SolveSpace version: 3.0~33b6e517 (current master, built with clang 4.0)
Operating system: Arch Linux x86-64
Expected behavior
Solvespace should have reported an error (since I'm pretty certain the model has issues that lead to a somewhat broken mesh) or it should successfully export the mesh.
Actual behavior
Solvespace hangs for a while, then crashes with a failed 'Cannot allocate memory' assertion.
Additional information
Open this file, click
File -> Export Triangle Mesh...
(doesn't matter which file type you choose).The text was updated successfully, but these errors were encountered: