Page MenuHome
Create Task
Maniphest T77664

Remesh spikes memory and crashes Blender
Closed, DuplicatePublic
Actions

Description

System Information
Operating system: Windows 10
Graphics card: NVIDIA GeForce RTX 2070

Blender Version
Broken: 2.83 and blender-2.90.0-9f7d84b656fb-windows64
Worked: No versions work

Short description of error

Memory spikes to 99% and CPU (AMD Ryzen Threadripper 2950X 16-core) goes to 35-70%, all fans engage --- and the computer holds in that pattern doing nothing for 5-10 minutes until Blender exits without warning.

Exact steps for others to reproduce the error

  1. Import .OBJ or .FBX file.
  2. Add Modifier
  3. Remesh

You can literally use any OBJ with 1,000 faces or more. Ours have 300,000 + faces, but this behavior is seen even when we decimate the meshes down to hundreds of faces. Bottom line, nothing can be re-meshed.

Related Objects

Event Timeline

J. Gregory (visionarymind) created this task.Jun 9 2020, 6:56 AM
Chingiz Jumagulov (Krayzmond) added a subscriber: Chingiz Jumagulov (Krayzmond).Jun 9 2020, 8:02 AM
Henrik Dick (weasel) changed the task status from Needs Triage to Needs Information from User.Jun 9 2020, 1:38 PM
Henrik Dick (weasel) added a subscriber: Henrik Dick (weasel).

Can you also provide information which remesh mode you used and how fine the voxel grid is in relation to your object? Did you try a more sparse voxel resolution? This really seems like a typical out of memory report.

J. Gregory (visionarymind) added a comment.EditedJun 10 2020, 2:12 AM

It is not possible to set any voxel settings. It does not even get that far. AS soon as I click "Remesh", Blender stops responding. The remesh properties block does not even show up. I have 64Gb of memory, and this is happening with 10Mb OBJ files with literally only a few vertices. Is there a console I can use to view backend processing tasks? Debugging would be easier if the application were throwing up errors.

Henrik Dick (weasel) added a comment.Jun 10 2020, 1:13 PM

Ok can you share one example blend file with the small obj imported and the obj file itself? I suspect, that maybe your object is huge in size (not in memory size). You can also check your Task Manager to check if you are running out of memory.

Robert Guetzkow (rjg) mentioned this in T77868: Remesh Voxel Size can be much to small by default (leading to crashes). 'Edit Voxel Size' operator can have wrong range.Jun 14 2020, 11:33 PM
Ankit Meel (ankitm) closed this task as a duplicate of T77868: Remesh Voxel Size can be much to small by default (leading to crashes). 'Edit Voxel Size' operator can have wrong range.Jun 15 2020, 8:33 AM
Zachary Comstock (SarahKitten2) added a subscriber: Zachary Comstock (SarahKitten2).Apr 7 2021, 6:16 PM

I had the same issue as you when trying to remesh. I realized my model was an stl and since stls can be weird I Just tried converting it to an obj and remeshing worked fine. Thought I'd post this incase anyone else is looking the issue up online.