Page MenuHome

Tris to quad crash blender with non manifold edge in model.
Closed, ResolvedPublic

Description

System Information
4GB RAM
Ubuntu 14.04
gtx 750 ti

Blender Version
Broken: 2.74 000dfc0
also for 2.74.5 a8adeeb

Short description of error
Blender is crashing when i am using tris to quads command.
I found that in mesh there is one non manifold edge. When i fix this edge (delete edge and fill hole), blender does not crash.

Exact steps for others to reproduce the error

  • open blend
  • pres alt+j
  • blender crash

Revisions and Commits

Event Timeline

Marián Kosa (keymaker) raised the priority of this task from to 90.
Marián Kosa (keymaker) updated the task description. (Show Details)
Marián Kosa (keymaker) edited a custom field.
Campbell Barton (campbellbarton) lowered the priority of this task from 90 to 30.Apr 22 2015, 4:58 PM

The mesh is corrupt,

bpy.context.object.data.validate(1)

Prints

BKE_mesh_validate_arrays: verts(1058), edges(3169), loops(6336), polygons(2112)
Edge 3168: is a duplicate of 108
Poly 1313 has invalid edge reference (3168), fixed using edge 108

So the question is - how did you get a mesh which is corrupt?
(importers should validate meshes they import)

So the question is - how did you get a mesh which is corrupt?

I receive stl file from client, but that worked fine.

I was able to replicate what i did.

  1. Open blend file with my mesh
  2. there you can see highlighted nonmanifold edge (only thing that holds whose two parts together)
  3. I needed it as separate pieces so i riped (v) those vertexes so i can select those parts as separate mesh (in face mode or how do you call it).
  4. after this separation, you should have corrupt mesh, the inner part. (at least for me it starts crashing again)
Campbell Barton (campbellbarton) raised the priority of this task from 30 to 50.

@Marián Kosa (keymaker), kudos for exposing this bug, this is from 2012 (since BMesh inclusion, 2.63).

damn, that's about time when i seriously started with blender.

If remember correctly, it bothered me few times before, but it looked like random crash. Anyway, thanks for fixing it.