Boolean produces corrupted geometry #38803

Closed
opened 2014-02-24 12:29:02 +01:00 by So3Datel · 11 comments

System Information
Windows 8.1 x64
Intel i5, GTX 560, 8GB RAM

Blender Version
2.69.0 (r60995) and 2.69 (b096845)

sorry for my English, I use Google translator.
I created object and added modifier Subdivision Surfatse, applied it.
With the aid of The Boolean modifier and cylinders cut out holes.
The Boolean modifier applied.
I got an object with holes (in blend file)
Now when I go into edit mode and select a vertex or edge, it's okay. But, when I select the polygons, Blender freezes.

http://www.youtube.com/watch?v=oKwoNublnOg

Т-100-140_1.blend

**System Information** Windows 8.1 x64 Intel i5, GTX 560, 8GB RAM **Blender Version** 2.69.0 (r60995) and 2.69 (b096845) sorry for my English, I use Google translator. I created object and added modifier Subdivision Surfatse, applied it. With the aid of The Boolean modifier and cylinders cut out holes. The Boolean modifier applied. I got an object with holes (in blend file) Now when I go into edit mode and select a vertex or edge, it's okay. But, when I select the polygons, Blender freezes. http://www.youtube.com/watch?v=oKwoNublnOg [Т-100-140_1.blend](https://archive.blender.org/developer/F78723/Т-100-140_1.blend)
Author

Changed status to: 'Open'

Changed status to: 'Open'
Author

Added subscriber: @AxelMening-4

Added subscriber: @AxelMening-4

Added subscriber: @DriesvanOosten

Added subscriber: @DriesvanOosten

Confirmed on linux x_64. In fact, it's even worse for me. If I open the blend file, go into edit mode and click on the icon that sets selection for face mode, blender already hangs
at exactly 100% cpu usage (it is maxing out one core, but not using others). A kill command from the console is required to shut blender down.

However, if I make a simple cube and intersect it with a cylinder, I don't have the problem. So there is something specific in the blend file that triggers this.

Confirmed on linux x_64. In fact, it's even worse for me. If I open the blend file, go into edit mode and click on the icon that sets selection for face mode, blender already hangs at exactly 100% cpu usage (it is maxing out one core, but not using others). A kill command from the console is required to shut blender down. However, if I make a simple cube and intersect it with a cylinder, I don't have the problem. So there is something specific in the blend file that triggers this.
Author

"So there is something specific in the blend file that triggers this"

Yes, many times I use Boolean operations, but this happens for the first time

"So there is something specific in the blend file that triggers this" Yes, many times I use Boolean operations, but this happens for the first time
Sergey Sharybin was assigned by Lukas Tönne 2014-02-24 14:19:06 +01:00
Member

Added subscribers: @Sergey, @LukasTonne

Added subscribers: @Sergey, @LukasTonne
Member

Opening the file and going into edit mode fails on bmesh assert:
https://developer.blender.org/diffusion/B/browse/master/source/blender/bmesh/intern/bmesh_core.c;b5aef37c27f5fb2a4bb4227253f81d886ddd796c$557

If i disable ASSERT_ABORT i can reproduce the freezing as well, it just gives lots of assert messages on stderr then.

I couldn't reproduce the faulty mesh by making my own boolean modifier and applying in recent Blender version. Could you please try repeating this procedure on a recent build from builder.blender.org (re-doing the boolean modifier and apply, not just opening the broken file).

@Sergey: I assume this is a problem with the recent boolean changes, so assigning to you. It may have been fixed since the mentioned build (14th february).

Opening the file and going into edit mode fails on bmesh assert: https://developer.blender.org/diffusion/B/browse/master/source/blender/bmesh/intern/bmesh_core.c;b5aef37c27f5fb2a4bb4227253f81d886ddd796c$557 If i disable ASSERT_ABORT i can reproduce the freezing as well, it just gives lots of assert messages on stderr then. I couldn't reproduce the faulty mesh by making my own boolean modifier and applying in recent Blender version. Could you please try repeating this procedure on a recent build from builder.blender.org (re-doing the boolean modifier and apply, not just opening the broken file). @Sergey: I assume this is a problem with the recent boolean changes, so assigning to you. It may have been fixed since the mentioned build (14th february).

Couple of things:

  • Boolean integration is fully rewritten now, so please give it a try with latest builds from http://builder.blender.org/download/
  • It's not possible to do anything with your file actually. it's totally lost now.. We do need .blend file before you hit any "Apply" on the boolean modifier. This way we can check where exactly mesh became corrupted.

So please try reproducing the issue from scratch using latest builds and let us know whether bug still happens (n this case provide .blend file at the stage boolean modifier is not applied yet). Or likely blender will just work for you.

Couple of things: - Boolean integration is fully rewritten now, so please give it a try with latest builds from http://builder.blender.org/download/ - It's not possible to do anything with your file actually. it's totally lost now.. We do need .blend file before you hit any "Apply" on the boolean modifier. This way we can check where exactly mesh became corrupted. So please try reproducing the issue from scratch using latest builds and let us know whether bug still happens (n this case provide .blend file at the stage boolean modifier is not applied yet). Or likely blender will just work for you.
Sergey Sharybin changed title from Blender not responding to Boolean produces corrupted geometry 2014-02-24 14:31:41 +01:00
Author

yes, I used the latest build and everything went well, the error is not repeated. thank you

yes, I used the latest build and everything went well, the error is not repeated. thank you

Changed status from 'Open' to: 'Resolved'

Changed status from 'Open' to: 'Resolved'

Coolie, considering the issue is solved then :)

Coolie, considering the issue is solved then :)
Sign in to join this conversation.
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
EEVEE & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
4 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#38803
No description provided.