Boolean union exact operation crashing on specific situation in newest 2.93.0 alpha #85948

New Issue

Alexandre Mano · 2021-02-24T12:21:03+01:00

Alexandre Mano commented

2021-02-24 12:21:03 +01:00

bug_report_booleans.blend

bug_report_booleans_modifier_on.blend

blender_system_info.txt

bug_report_booleans_modifier_on.crash.txt

System Information
Operating system: Windows 10
Graphics card: Nvidia RTX 2060

Blender Version
Broken: 2.93.0-b2c7ea6d82c4 (the previous two daily alpha versions are also crashing)
Worked: 2.93.0-461d4fc1aae2 (previous week I think)

Caused by a3f091d7ce

Description
Boolean union with Exact operation enabled in this specific mesh crashes blender, either during activation of the modifier using the newest version of the alpha or while opening the blend file which was saved in a previous alpha version (if the modifier was left enabled during saving on previous blender alpha versions). I have tried several other similar objects I was working on and most result in a crash when this kind of boolean is enabled.

Might be occuring due to something on my side, or the specific type/density of brick wall mesh im trying to boolean, however i've tried with no comunity addons and even with factory settings, blender crashes...

Exact steps for others to reproduce the error
Both uploaded files are the same (only difference is that one opens with the boolean modifier disabled and the other with the modifier enabled).
For the error to occur, blender should either crash while opening the file "bug_report_booleans_modifier_on.blend" or while enabling the last boolean for the tower in file "bug_report_booleans.blend"

[bug_report_booleans.blend](https://archive.blender.org/developer/F9834435/bug_report_booleans.blend) [bug_report_booleans_modifier_on.blend](https://archive.blender.org/developer/F9834434/bug_report_booleans_modifier_on.blend) [blender_system_info.txt](https://archive.blender.org/developer/F9834446/blender_system_info.txt) [bug_report_booleans_modifier_on.crash.txt](https://archive.blender.org/developer/F9834445/bug_report_booleans_modifier_on.crash.txt) **System Information** Operating system: Windows 10 Graphics card: Nvidia RTX 2060 **Blender Version** Broken: 2.93.0-b2c7ea6d82c4 (the previous two daily alpha versions are also crashing) Worked: 2.93.0-461d4fc1aae2 (previous week I think) Caused by a3f091d7ce **Description** Boolean union with Exact operation enabled in this specific mesh crashes blender, either during activation of the modifier using the newest version of the alpha or while opening the blend file which was saved in a previous alpha version (if the modifier was left enabled during saving on previous blender alpha versions). I have tried several other similar objects I was working on and most result in a crash when this kind of boolean is enabled. Might be occuring due to something on my side, or the specific type/density of brick wall mesh im trying to boolean, however i've tried with no comunity addons and even with factory settings, blender crashes... **Exact steps for others to reproduce the error** Both uploaded files are the same (only difference is that one opens with the boolean modifier disabled and the other with the modifier enabled). For the error to occur, blender should either crash while opening the file "bug_report_booleans_modifier_on.blend" or while enabling the last boolean for the tower in file "bug_report_booleans.blend"

Alexandre Mano commented

2021-02-24 12:21:03 +01:00

Added subscriber: @Xande

Philipp Oeser commented

2021-02-24 12:32:31 +01:00

Added subscriber: @lichtwerk

Philipp Oeser commented

2021-02-24 12:32:31 +01:00

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

Philipp Oeser commented

2021-02-24 12:32:31 +01:00

Can confirm, will check

Philipp Oeser commented

2021-02-24 12:54:48 +01:00

Added subscriber: @howardt

Philipp Oeser commented

2021-02-24 12:54:48 +01:00

Caused by a3f091d7ce

@howardt : mind having a look?

Caused by a3f091d7ce @howardt : mind having a look?

Howard Trickey self-assigned this 2021-02-24 13:08:25 +01:00

Howard Trickey commented

2021-02-25 18:07:04 +01:00

I have discovered the cause of the crash. The new code does its own triangulation using constrained delaunay triangulation, instead of the polyfill code that the old codepath used. I should probably just switch to using that old code path, which will be faster anyway (I was, probably out of an exceeding amount of caution, using the mulitprecision version of the CDT code). This might take a few days to fix. Meanwhile, you (bug reporter) might want to look for faces that look like this:

which are hard to triangulate (at least, using our typical method of projecting along the dominant normal axis), so with these faces there, you may get shading issues.

I have discovered the cause of the crash. The new code does its own triangulation using constrained delaunay triangulation, instead of the polyfill code that the old codepath used. I should probably just switch to using that old code path, which will be faster anyway (I was, probably out of an exceeding amount of caution, using the mulitprecision version of the CDT code). This might take a few days to fix. Meanwhile, you (bug reporter) might want to look for faces that look like this: ![Screen Shot 2021-02-25 at 12.02.01 PM.png](https://archive.blender.org/developer/F9839154/Screen_Shot_2021-02-25_at_12.02.01_PM.png) which are hard to triangulate (at least, using our typical method of projecting along the dominant normal axis), so with these faces there, you may get shading issues.

Alexandre Mano commented

2021-02-25 19:17:08 +01:00

Thanks for the advice. Good to know that instead of helping improving I am actually making you have to take a few steps back...
I wasn't aware that faces like this cound be an issue... back to quad topology I go then.

Anyway, I actually noticed those shading issues after applying the booleans and triangulating similar models of the same set in previous alpha versions
I usually just fixed those manually and quickly by filling in the faces correctly.
These facesswere cut very roughly and quickly with the knife tool, as these models were only intended for small size 3d printing and there was no need for good shading nor much detail on the affected regions.

Also, not sure if the best place for this, but love your work on booleans, the exact boolean solver has been a gamechanger for me since its implementation, just wanted to say thanks for that!

Thanks for the advice. Good to know that instead of helping improving I am actually making you have to take a few steps back... I wasn't aware that faces like this cound be an issue... back to quad topology I go then. Anyway, I actually noticed those shading issues after applying the booleans and triangulating similar models of the same set in previous alpha versions I usually just fixed those manually and quickly by filling in the faces correctly. These facesswere cut very roughly and quickly with the knife tool, as these models were only intended for small size 3d printing and there was no need for good shading nor much detail on the affected regions. Also, not sure if the best place for this, but love your work on booleans, the exact boolean solver has been a gamechanger for me since its implementation, just wanted to say thanks for that!

blender-admin commented

2021-02-28 00:51:48 +01:00

This issue was referenced by f3d60c68ef

This issue was referenced by f3d60c68ef469a9a9de8d5dc4d7dbbd168950ceb

Howard Trickey commented

2021-02-28 00:52:41 +01:00

Changed status from 'Confirmed' to: 'Resolved'

Howard Trickey closed this issue

2021-02-28 00:52:41 +01:00

Howard Trickey commented

2021-02-28 00:56:55 +01:00

The change I made fixed the crash. But I do see that your example takes an awful long time to Boolean. Sorry!. This will be a good example for future performance tuning.

Alexandre Mano commented

2021-03-05 13:11:47 +01:00

Back again with a similar issue on the same project, although im unsure if I should be posting it on this since it is already tagged as closed...

Same issue as before, crash while enabling boolean. File is a part of a model I narrowed out for this report.
I'm mostly sure I can easily fix up the model mesh to prevent the crash, however i thought it could be useful to post it in here.

Just open the file, select the main model and enable the boolean, blender should crash after that...

Blender 2.93.0-b5d154f400e4

Boolean Issue 2.blend

Back again with a similar issue on the same project, although im unsure if I should be posting it on this since it is already tagged as closed... Same issue as before, crash while enabling boolean. File is a part of a model I narrowed out for this report. I'm mostly sure I can easily fix up the model mesh to prevent the crash, however i thought it could be useful to post it in here. Just open the file, select the main model and enable the boolean, blender should crash after that... Blender 2.93.0-b5d154f400e4 [Boolean Issue 2.blend](https://archive.blender.org/developer/F9869835/Boolean_Issue_2.blend)

Philipp Oeser commented

2021-03-05 13:50:24 +01:00

@Xande : please report this separately (it probably has a different cause)

Thomas Dinges added this to the 2.93 LTS milestone 2023-02-07 18:46:31 +01:00

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 union exact operation crashing on specific situation in newest 2.93.0 alpha #85948