Page MenuHome

Voxel remesh crash
Closed, ResolvedPublic


System Information
Operating system: Windows-10-10.0.18362 64 Bits
Graphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 441.66

Blender Version
Broken: version: 2.81 (sub 16), branch: master, commit date: 2019-12-04 11:32, hash: rBf1aa4d18d49d
Worked: (optional)

Short description of error
the voxel remesh button crash bledner if you set the Voxel Size to 0m

Exact steps for others to reproduce the error

  1. Open blender and go to the Object Data Properties
  2. Go to the Remesh and set Voxel Size to 0m and adaptivity to 1m
  3. Click on the Voxel Remesh button and blender will crash

keep up the great work

Event Timeline

kin malmin (star) renamed this task from Voxel remehser crash to Voxel remesh crash.Dec 28 2019, 12:16 PM
kin malmin (star) created this task.
Jacques Lucke (JacquesLucke) changed the task status from Needs Triage to Confirmed.Dec 28 2019, 1:16 PM

I can reproduce that.
@Pablo Dobarro (pablodp606) While the voxel size cannot be set to 0, it can be set to 0.00001. Apparently this value is too close to the machine epsilon which causes openvdb to raise an ArithmeticError. I assume you can just increase the min value a bit to avoid that issue.

Philipp Oeser (lichtwerk) claimed this task.

Cannot reproduce an instant crash.

This just goes calculating and eating RAM.
Doing this with on the default cube with a voxel size of 0.001m (1mm) will already end up with a mesh of ~50million tris and eat up ~10GB RAM.
I think it should be expected to reach the limits of most computers if you are doing this with a voxel size of 0.0001m (effective factor 1000 compared to the above)?

So, thanks for the report, but it appears this crashes in the end because Blender ran out of memory.
While we want to improve Blender to handle such cases more gracefully, this is not currently considered a bug.

Philipp Oeser (lichtwerk) reopened this task as Confirmed.Dec 28 2019, 1:20 PM

Ah, OK, get it now, sorry for the noise...