Seperate crashes with Zero Faces. #66657
Labels
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
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#66657
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
{F7581766}System Information
Operating system: Windows
Graphics card: Nvidia
Blender Version
Broken: 2.80,
3b4054cb58
Separate in Edit Mode will crash when mesh has faces with zero area. It happens in a mesh that has been imported. Fixed the mesh with Print3D tools, checked the mesh with it and removed the Zero Faces.
Exact steps for others to reproduce the error
Based on the default startup or an attached .blend file (as simple as possible).
Added subscriber: @real_3ddy
Added subscriber: @lichtwerk
Cannot reproduce here (tried with default suzanne, scaled two faces to zero,
P
>Selection
, no crash.. -- and yes, these two faces were reported by the Print3D toolbox as well...).Mind sharing the .blend with the offending geometry?
I've uploaded a file. Just select the faces (left half of the object) and hit P. It crashed.
The mesh in its original form is a building. But because of the work created a deformed mesh to make it unrecognizable. Still the bug is there.
This might not be the face area alone, I'm already getting assert when opening that file (with the deforming modifiers) or entering editmode (without the modifiers):
BMESH_ASSERT failed: /blender/source/blender/bmesh/intern/bmesh_core.c, bmesh_elem_check(), 735 at 'err == 0'
where
err
is(IS_FACE_LOOP_VERT_NOT_IN_EDGE | IS_FACE_LOOP_WRONG_RADIAL_LENGTH | IS_FACE_LOOP_DUPE_VERT | IS_FACE_LOOP_DUPE_EDGE) (53477376)
so the mesh seems to be corrupt to begin with. Before digging deeper:
It's imported with arma, so not maintained by Blender. I use it for importing objects into Blender from our software.
Maybe it is possible that Blender is not Crashing but instead give you a message that the mesh is corrupt.
Added subscriber: @mont29
@mont29: I think we are not doing this all over the place for performance reasons, right?
As a "workaround" you could ensure valid geometry after the import by running
validate
on your mesheshttps://docs.blender.org/api/master/bpy.types.Mesh.html?#bpy.types.Mesh.validate
So in your case, this line fixes it:
bpy.data.meshes['0.002'].validate()
In fact, most importers do this (validate), so it might be good to report this to the Arma-Toolbox author(s)?
I downloaded Arma-Toolbox and had a quick look, but apart from a (commented out) .validate, it is not used anywhere...
Awesome! Thx for checking this out! You or I can close this bug report then I think.
Changed status from 'Open' to: 'Resolved'