Boolean modifier making Blender lag and freeze #103612

New Issue

Anton Lövdahl · 2023-01-03T14:23:53+01:00

Anton Lövdahl commented

2023-01-03 14:23:53 +01:00

System Information
Operating system: Windows 11 Home, Version: 22H2, OS-version: 22621.963, 64 Bits
Graphics card: NVIDIA GeForce RTX 3070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 527.56

Blender Version
Broken: version: 3.4.1, branch: blender-v3.4-release, commit date: 2022-12-20 08:50, hash: ef9ca44dee

Short description of error
Boolean modifier cause Blender to run slowly and freeze when trying to move the objects affected by the modifier. This happens when you want one object to cut through another. From my tests, the more complex the mesh is, (more corners, edges, and faces) the object you want to cut have, the slower Blender will run when using the boolean modifier before applying it.

In the first attached .blend file I tried to cut some detail on my flashlight, but when I have used the eyedropper tool from the boolean on the other object blender completely freezes. In the second file, I used a more simple shape to cut through the same mesh. Blender did not crash, but is extreamly laggy.

Exact steps for others to reproduce the error
*Open flashlight1.blend file and select the flashlight
*Move around the object with G and right click cancel movement, it should look normal
*Do the same thing with the cylinders, everything works fine
*Select the flashlight and use boolean modifier
*Use the eyedropp tool on any of the cylinders
*Now select the flashlight or the cylinders again and try move around with G then cancel movement
*Blender should freeze
*If Blender unfreezes, delete boolean modifier
*Move objects around with G, everything should be fine again.

*Now do the exact same thing with the flahlight2.blend file but use the boolean eyedropp tool on cube
*Blender should not freeze, but lag a lot

*Last open booleantest.blend file
*Use boolean modifier on cube
*Select eyedropper tool on sphere
*Move around any object G, it works fine
*Delete boolean modifier
*Subdivide both objects in edit mode
*Select one mesh, go to edit mode, right click and then subdivide
*Do this for both meshes 3 or 4 times
*Add boolean modifier to cube
*Select eyedropper tool on sphere
*Move around any object with G
*Blender should be laggy

flashlight1.blend
flashlight2.blend
booleantest.blend

Hope this helps

**System Information** Operating system: Windows 11 Home, Version: 22H2, OS-version: 22621.963, 64 Bits Graphics card: NVIDIA GeForce RTX 3070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 527.56 **Blender Version** Broken: version: 3.4.1, branch: blender-v3.4-release, commit date: 2022-12-20 08:50, hash: `ef9ca44dee` **Short description of error** Boolean modifier cause Blender to run slowly and freeze when trying to move the objects affected by the modifier. This happens when you want one object to cut through another. From my tests, the more complex the mesh is, (more corners, edges, and faces) the object you want to cut have, the slower Blender will run when using the boolean modifier before applying it. In the first attached .blend file I tried to cut some detail on my flashlight, but when I have used the eyedropper tool from the boolean on the other object blender completely freezes. In the second file, I used a more simple shape to cut through the same mesh. Blender did not crash, but is extreamly laggy. **Exact steps for others to reproduce the error** *Open flashlight1.blend file and select the flashlight *Move around the object with G and right click cancel movement, it should look normal *Do the same thing with the cylinders, everything works fine *Select the flashlight and use boolean modifier *Use the eyedropp tool on any of the cylinders *Now select the flashlight or the cylinders again and try move around with G then cancel movement *Blender should freeze *If Blender unfreezes, delete boolean modifier *Move objects around with G, everything should be fine again. *Now do the exact same thing with the flahlight2.blend file but use the boolean eyedropp tool on cube *Blender should not freeze, but lag a lot *Last open booleantest.blend file *Use boolean modifier on cube *Select eyedropper tool on sphere *Move around any object G, it works fine *Delete boolean modifier *Subdivide both objects in edit mode *Select one mesh, go to edit mode, right click and then subdivide *Do this for both meshes 3 or 4 times *Add boolean modifier to cube *Select eyedropper tool on sphere *Move around any object with G *Blender should be laggy [flashlight1.blend](https://archive.blender.org/developer/F14110989/flashlight1.blend) [flashlight2.blend](https://archive.blender.org/developer/F14110990/flashlight2.blend) [booleantest.blend](https://archive.blender.org/developer/F14110991/booleantest.blend) Hope this helps

Anton Lövdahl commented

2023-01-03 14:23:53 +01:00

Added subscriber: @AntonL020

Iliya Katushenock commented

2023-01-03 15:50:11 +01:00

Added subscriber: @mod_moder

Iliya Katushenock commented

2023-01-03 15:50:11 +01:00

Hello. Yes, this is a very slow operation. One of the slowest among all that is. And it strongly depends on the size of the geometry. And any operations cause updates to this. So yeah, I don't see the bug.
Of course, maybe this example demonstrates some kind of over-dimensional drop in speed. But I experimented and did not notice this. Maybe some tables with numbers that differ in degrees due to simple things would make sense.
But so far I do not see the structure for investigating the problem.

Hello. Yes, this is a very slow operation. One of the slowest among all that is. And it strongly depends on the size of the geometry. And any operations cause updates to this. So yeah, I don't see the bug. Of course, maybe this example demonstrates some kind of over-dimensional drop in speed. But I experimented and did not notice this. Maybe some tables with numbers that differ in degrees due to simple things would make sense. But so far I do not see the structure for investigating the problem.

Iliya Katushenock commented

2023-01-03 15:55:59 +01:00

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

Anton Lövdahl commented

2023-01-03 16:32:38 +01:00

Would a video demonstration of how much it lags for me help? Not sure how I can see the numbers in performance difference.

Iliya Katushenock commented

2023-01-03 16:39:05 +01:00

Of course. Based on its results, it will already be clear what happens next.

Anton Lövdahl commented

2023-01-03 17:31:11 +01:00

Here is a video of how it looks for me. This time blender even crashed
video – Gjord med Clipchamp.mp4

Here is a video of how it looks for me. This time blender even crashed [video – Gjord med Clipchamp.mp4](https://archive.blender.org/developer/F14111507/video___Gjord_med_Clipchamp.mp4)

Iliya Katushenock commented

2023-01-03 17:40:01 +01:00

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

Pratik Borhade commented

2023-01-04 06:08:57 +01:00

Added subscriber: @PratikPB2123

Pratik Borhade commented

2023-01-04 06:08:57 +01:00

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

Pratik Borhade closed this issue

2023-01-04 06:08:57 +01:00

Pratik Borhade commented

2023-01-04 06:08:57 +01:00

Hi, thanks for the report. Can you check CPU usage at the time of freeze?
I'm not able to reproduce this issue. As @mod_moder said Indeed there is performance drop calculations on heavy geometry.
Changing solve to Fast might help you to some extent.
Please also check with factory settings in case any add-ons in interfering: {nav File > Defaults . Load Factory Settings}
Reports about performance are not handled on tracker so closing this report:

While we do continue to work on improving performance in general, potential performance improvements are not handled as bug reports.
To improve performance, consider using less complex geometry, simpler shaders and smaller textures.

(https://wiki.blender.org/wiki/Reference/Not_a_bug)

Hi, thanks for the report. Can you check CPU usage at the time of freeze? I'm not able to reproduce this issue. As @mod_moder said Indeed there is performance drop calculations on heavy geometry. Changing solve to `Fast` might help you to some extent. Please also check with factory settings in case any add-ons in interfering: {nav File > Defaults . Load Factory Settings} Reports about performance are not handled on tracker so closing this report: > While we do continue to work on improving performance in general, potential performance improvements are not handled as bug reports. > To improve performance, consider using less complex geometry, simpler shaders and smaller textures. (https://wiki.blender.org/wiki/Reference/Not_a_bug)

Anton Lövdahl commented

2023-01-04 16:05:50 +01:00

Thanks for the reply. CPU usage looked normal during freeze. I will try to use a mesh with less geometry. :)

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 making Blender lag and freeze #103612