Boolean modifier crashes/freezes Blender using intersect (or consumes much memory) #87795

New Issue

RT · 2021-04-25T10:38:12+02:00

RT commented

2021-04-25 10:38:12 +02:00

System Information
Operating system: Linux-5.4.0-72-generic-x86_64-with-glibc2.31 64 Bits
Graphics card: Mesa DRI Intel(R) HD Graphics 4600 (HSW GT2) Intel Open Source Technology Center 4.5 (Core Profile) Mesa 20.2.6

Blender Version
Broken: version: 2.93.0 Beta, branch: master, commit date: 2021-04-24 18:46, hash: f7afd78b80
Worked: Last Worked in 2.92 (see video-Animation below)

Short description of error

Repeated Crash using Boolean modifier - Intersect -
Solver: Exact
Solver Options: Self

Writing: /tmp/section.crash.txt
Segmentation fault (core dumped)

section.crash.txt

Exact steps for others to reproduce the error

Open up downloaded attached file called section.blend this file will open fine
Change the settings to:
**Solver:Exact
**Solver Options:Self

Image below:

Crash

section.blend

**System Information** Operating system: Linux-5.4.0-72-generic-x86_64-with-glibc2.31 64 Bits Graphics card: Mesa DRI Intel(R) HD Graphics 4600 (HSW GT2) Intel Open Source Technology Center 4.5 (Core Profile) Mesa 20.2.6 **Blender Version** Broken: version: 2.93.0 Beta, branch: master, commit date: 2021-04-24 18:46, hash: `f7afd78b80` Worked: Last Worked in 2.92 (see video-Animation below) **Short description of error** ``` Repeated Crash using Boolean modifier - Intersect - Solver: Exact Solver Options: Self ``` Writing: /tmp/section.crash.txt Segmentation fault (core dumped) [section.crash.txt](https://archive.blender.org/developer/F10165533/section.crash.txt) **Exact steps for others to reproduce the error** 1) Open up downloaded attached file called **section.blend** this file will open fine 2) Change the settings to: **Solver:**Exact** **Solver Options:**Self** Image below: ![screenshot-2021-06-10-07-04-09.png](https://archive.blender.org/developer/F10165538/screenshot-2021-06-10-07-04-09.png) 3) Crash [section.blend](https://archive.blender.org/developer/F10037087/section.blend)

RT commented

2021-04-25 10:38:12 +02:00

Added subscriber: @Still

Falk David commented

2021-04-27 11:46:46 +02:00

Added subscriber: @filedescriptor

Falk David commented

2021-04-27 11:46:46 +02:00

@Still

And the 3D sectioning no longer works as expected (see animation of 2d and 3d sectioning working in 2.92 below)

Please only include one issue in a single report. It seems like these are completely separate issues, so please open another report for the "3D sectioning" issue and keep this report for the crash only.

@Still > And the 3D sectioning no longer works as expected (see animation of 2d and 3d sectioning working in 2.92 below) Please only include one issue in a single report. It seems like these are completely separate issues, so please open another report for the "3D sectioning" issue and keep this report for the crash only.

RT commented

2021-04-27 16:22:15 +02:00

Ok, I'll separate all three issues and add them as separate issues...I'll leave this one to deal with the crash.

RT changed title from ~~Boolean modifier crash using intersect~~ to Boolean modifier crashes Blender using intersect

2021-04-28 14:42:05 +02:00

Ankit Meel commented

2021-06-10 12:30:06 +02:00

Added subscriber: @ankitm

Ankit Meel commented

2021-06-10 12:30:06 +02:00

Changed status from 'Needs Triage' to: 'Needs User Info'

Ankit Meel commented

2021-06-10 12:30:06 +02:00

What are the steps to get the crash ? The GIF shows the issue you show in #87866 (Boolean modifier - Intersect option - not working / artifacts while doing 3D Sectioning).

RT commented

2021-06-10 13:10:55 +02:00

This is similar but this will CRASH Blender I attached the generated crash file this time sorry for not including it the first time.

Clearer Steps with image: 1) Open up downloaded attached file calledsection.blend (included in the above report) this file will open fine
2) Change the settings to:
**Solver:Exact
**Solver Options:Self

Image below:

Crash
See attached crash file
Writing: /tmp/section.crash.txt
Segmentation fault (core dumped)

section.crash.txt

This is similar but this will **CRASH** Blender I attached the generated crash file this time sorry for not including it the first time. **`Clearer Steps with image: `**1) Open up downloaded attached file called**section.blend** (*included in the above report*) this file will open fine 2) Change the settings to: **Solver:**Exact** **Solver Options:**Self** Image below: ![screenshot-2021-06-10-07-04-09.png](https://archive.blender.org/developer/F10165538/screenshot-2021-06-10-07-04-09.png) 3) Crash See attached crash file Writing: /tmp/section.crash.txt Segmentation fault (core dumped) [section.crash.txt](https://archive.blender.org/developer/F10165533/section.crash.txt)

Ankit Meel commented

2021-06-10 13:25:58 +02:00

Changed status from 'Needs User Info' to: 'Needs Triage'

Ankit Meel commented

2021-06-10 13:25:58 +02:00

I'm redoing the steps in 0efb627bbd, but so far I see memory increase only.
I'll try blender 2.93 also.

I removed the info in the top level box that has been moved to other reports.

I'm redoing the steps in 0efb627bbd, but so far I see memory increase only. I'll try blender 2.93 also. I removed the info in the top level box that has been moved to other reports.

Ankit Meel commented

2021-06-10 21:19:24 +02:00

I ran blender 2.93 for about 40 minutes before killing it because it didn't crash, nor returned to usable state. Memory at the time of killing was about 24 GB for a while then.

RT commented

2021-06-15 06:54:03 +02:00

Do you need anything else from me?

Pratik Borhade commented

2021-07-09 08:40:38 +02:00

Added subscriber: @PratikPB2123

Pratik Borhade commented

2021-07-09 08:40:38 +02:00

No crash here but consuming too much of memory. Also: as Ankit said, it did not return to working state.

For me 2.92 also has the same issue

No crash here but consuming too much of memory. Also: as Ankit said, it did not return to working state. For me 2.92 also has the same issue

Philipp Oeser commented

2021-09-24 15:34:52 +02:00

Added subscribers: @howardt, @lichtwerk

Philipp Oeser commented

2021-09-24 15:34:52 +02:00

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

Philipp Oeser commented

2021-09-24 15:34:52 +02:00

This does not sound right.

Here is where it hangs for me:

Will confirm for now, @howardt : could you check on this?

This does not sound right. Here is where it hangs for me: ![image.png](https://archive.blender.org/developer/F10571242/image.png) Will confirm for now, @howardt : could you check on this?

Philipp Oeser changed title from ~~Boolean modifier crashes Blender using intersect~~ to Boolean modifier crashes/freezes Blender using intersect (or consumes much memory)

2021-09-24 15:35:32 +02:00

Howard Trickey commented

2021-09-26 19:07:46 +02:00

So I think this is just a performance bug. There are just too many self intersections, because currently I treat touching at a vertex or exactly sharing an edge as a self-intersection (of course, neither of those contribute any new geometry at the end, but the intermediate algorithms all consider them). I'm investigating further now to make sure that is really all that is going on here.

It is possible that the crash that the original reporter reported was due to running out of memory. For me, as with others here who have tested, it is just taking "forever".

So I think this is just a performance bug. There are just too many self intersections, because currently I treat touching at a vertex or exactly sharing an edge as a self-intersection (of course, neither of those contribute any new geometry at the end, but the intermediate algorithms all consider them). I'm investigating further now to make sure that is really all that is going on here. It is possible that the crash that the original reporter reported was due to running out of memory. For me, as with others here who have tested, it is just taking "forever".

Howard Trickey commented

2021-09-26 22:15:10 +02:00

Changed status from 'Confirmed' to: 'Archived'

Howard Trickey closed this issue

2021-09-26 22:15:10 +02:00

Howard Trickey commented

2021-09-26 22:15:10 +02:00

I think there is nothing for me to fix immediately here. I believe that if I let it run for 2 hours on my machine it would finish.

The big problem is that the result of the self intersection is a monster with almost 5 million triangles, a large number of which are non-manifold. This is because the input turbine object has a very messy bottom section, with lots of non-manifold vertices and (I think) very many skinny triangles. I believe if that model were cleaned up, this boolean would work acceptably. A workaround might be to separate that messy bottom out into a separate object and leave it out of the Boolean, and then weld it in later.

I can imagine (fairly large) changes to my code that could make this case run acceptably fast, but those are long term things, not something that I would regard as a bug fix for this particular case.

I think there is nothing for me to fix immediately here. I believe that if I let it run for 2 hours on my machine it would finish. The big problem is that the result of the self intersection is a monster with almost 5 million triangles, a large number of which are non-manifold. This is because the input turbine object has a very messy bottom section, with lots of non-manifold vertices and (I think) very many skinny triangles. I believe if that model were cleaned up, this boolean would work acceptably. A workaround might be to separate that messy bottom out into a separate object and leave it out of the Boolean, and then weld it in later. I can imagine (fairly large) changes to my code that could make this case run acceptably fast, but those are long term things, not something that I would regard as a bug fix for this particular case.

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

Boolean modifier crashes/freezes Blender using intersect (or consumes much memory) #87795