Crash With Exact Self Booleans With > ~1.5M Triangles #83012

New Issue

Philip Holzmann · 2020-11-25T18:34:59+01:00

Philip Holzmann commented

2020-11-25 18:34:59 +01:00

System Information
Operating system: Windows 64 bit
Graphics card: Nivida GTX 750 Ti

Blender Version
Broken: 2.91.0 release
Worked: never?

Short description of error
High poly meshes cause the exact booleans to crash, due to a failed memory allocation. This, however, only occurs with the Self flag checked.
I have 16 GB of RAM, of which only about 2 GB is used, and the allocation also seems to be exactly 2 GB, which is quite suspicious. I'm not sure what's going wrong here.

For me, this makes the exact boolean unusable for combining parts of a large sculpt, since the Collection mode implies Self.

Exact steps for others to reproduce the error
boolean_highpoly.blend
Tick the Self in the modifier options. Crash ensues after a few seconds.

blender_system_info.txt
blender_debug_output.txt

**System Information** Operating system: Windows 64 bit Graphics card: Nivida GTX 750 Ti **Blender Version** Broken: 2.91.0 release Worked: never? **Short description of error** High poly meshes cause the exact booleans to crash, due to a failed memory allocation. This, however, only occurs with the *Self* flag checked. I have 16 GB of RAM, of which only about 2 GB is used, and the allocation also seems to be *exactly* 2 GB, which is quite suspicious. I'm not sure what's going wrong here. For me, this makes the exact boolean unusable for combining parts of a large sculpt, since the *Collection* mode implies *Self*. **Exact steps for others to reproduce the error** [boolean_highpoly.blend](https://archive.blender.org/developer/F9373866/boolean_highpoly.blend) Tick the *Self* in the modifier options. Crash ensues after a few seconds. [blender_system_info.txt](https://archive.blender.org/developer/F9373876/blender_system_info.txt) [blender_debug_output.txt](https://archive.blender.org/developer/F9373873/blender_debug_output.txt)

Philip Holzmann commented

2020-11-25 18:35:00 +01:00

Added subscriber: @Foaly

Philip Holzmann changed title from ~~Crash With Exact Seö > ~1.5M Triangles~~ to Crash With Exact Self Booleans With > ~1.5M Triangles

2020-11-25 18:35:23 +01:00

Robert Guetzkow commented

2020-11-26 01:04:05 +01:00

Added subscriber: @rjg

Robert Guetzkow commented

2020-11-26 01:04:05 +01:00

Changed status from 'Needs Triage' to: 'Archived'

Robert Guetzkow closed this issue

2020-11-26 01:04:05 +01:00

Robert Guetzkow commented

2020-11-26 01:04:05 +01:00

The measurements of the used memory seem to be incorrect. After enabling Self the memory usage peaks at approximately 19.4 GB. This means you're running out of memory. You will either have to use less complex mesh or a computer with more RAM.

The measurements of the used memory seem to be incorrect. After enabling *Self* the memory usage peaks at approximately 19.4 GB. This means you're running out of memory. You will either have to use less complex mesh or a computer with more RAM.

Philip Holzmann commented

2020-12-06 10:14:42 +01:00

I have tried this again with a debugger attached. At the time of crash, Blender has only allocated a total of ~4GB.
I will try to investigate further.

I have tried this again with a debugger attached. At the time of crash, Blender has only allocated a total of ~4GB. I will try to investigate further.

Philip Holzmann commented

2020-12-06 13:55:22 +01:00

Okay, I must have misinterpreted something here, it appears the crash was indeed due to running out of memory.
The crash happened in source\blender\blenlib\intern\mesh_intersect.cc:trimesh_nary_intersect() in the call itt_map.reserve(tri_ov.overlap().size());.

I tried replacing the hash map with a regular std::unordered_map, which results in it running without crashing and peaking at 7.8 GB (less than half the peak you reported!).
Due to this, I think it might be worth looking into replacing Blender's own hash map implementation, at least for the booleans.

Okay, I must have misinterpreted something here, it appears the crash was indeed due to running out of memory. The crash happened in `source\blender\blenlib\intern\mesh_intersect.cc:trimesh_nary_intersect()` in the call `itt_map.reserve(tri_ov.overlap().size());`. I tried replacing the hash map with a regular `std::unordered_map`, which results in it running without crashing and peaking at 7.8 GB (less than half the peak you reported!). Due to this, I think it might be worth looking into replacing Blender's own hash map implementation, at least for the booleans.

Sign in to join this conversation.

No Label

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Crash With Exact Self Booleans With > ~1.5M Triangles #83012