Page MenuHome

Crash on collection visibility toggle (corrupted mesh)
Open, Confirmed, MediumPublic

Description

System Information
Operating system: Darwin-18.7.0-x86_64-i386-64bit 64 Bits
Graphics card: AMD Radeon Pro Vega 20 OpenGL Engine ATI Technologies Inc. 4.1 ATI-2.11.20

Blender Version
Broken: version: 2.81 (sub 15), branch: master, commit date: 2019-10-14 16:46, hash: rB879d269e8769
Worked: (optional)

Short description of error
Blender brutally crashed without callstack

Exact steps for others to reproduce the error

  • Open the blend file (I did not manage to prune the materials, sorry for the big file :-/ )
  • Enable the "murs" collection (check the box)
  • Crash

Note: the blend file was created from scratch in Blender 2.8 and it started crashing without apparent reasons.

Details

Type
Bug

Event Timeline

It also crash when expanding the polygon data in the "Data Api" of the mesh "Cube.033" inside the the "murs" collection

Jacques Lucke (JacquesLucke) lowered the priority of this task from Needs Triage by Developer to Confirmed, High.EditedOct 16 2019, 3:44 PM

I can reproduce the issue. Looks like an uninitialized mesh loops array after modifier evaluation. Checking...

Jacques Lucke (JacquesLucke) lowered the priority of this task from Confirmed, High to Confirmed, Medium.Oct 16 2019, 3:56 PM

Turns out, the file is already broken when loaded.

Did you model the geometry yourself, or is it generated by an addon? (I see there is a mesh with "Archipack" in the name, but I don't know how that addon works exactly)
If it is generated, then the bug is probably in the addon.

You can run [mesh.validate() for mesh in D.meshes] in the Python Console in Blender after opening the file to fix it.

Hi there,
Stair entity was working since 2.79 without any known issue, so it's probably not a mesh generation issue on the addon side, would crash at creation / update time.

@stephen leger (stephen_leger) It might be, that Blender 2.8 crashes earlier now when certain mesh data is uninitialized. Can you run mesh.validate(verbose=True) on the mesh the addon generates? Then check the terminal to see if there are any errors.

Ok validating geometry on another file this is what i get
Vertex 3: has zero normal

In archipack 1.2.8x the snap helper is a single vertex entity made to allow snap. So a 0 vertex normal looks not so weired ?

The error is reported on entity made of edges only, without any faces,
so at some point vertex normal is quite likely to be 0.
This happen on "Reference point", "Compass" and "Cutters".

I see, Blender expects normalized normals in a valid mesh. I'm not sure how performance critical the mesh generation in Archipack is. Maybe you can just run the validate function after every mesh generation.

I also found this "0 vertex normal" issue. However, that was not the reason for the crash. Maybe you can investigate the file from @Jerome Scholler (jscholler) and see if the invalid geometry was created using the addon or if it was created differently? I guess it should be easy for you to recognize a mesh your code generated.

Not related to archipack's generated geometry
Cube.003
BKE_mesh_validate_arrays: Loop 5912 is unused.
BKE_mesh_validate_arrays: Edge 518: v1 index out of range, 4294901760
mesh_validate_customdata: CustomDataLayer type 16 has some invalid data

Related to archipack's snap helper
BKE_mesh_validate_arrays: Vertex 0: has zero normal, assuming Z-up normal

Ok, thanks. @Jerome Scholler (jscholler), please try to remember how you created this object.

Did you model the geometry yourself, or is it generated by an addon? (I see there is a mesh with "Archipack" in the name, but I don't know how that addon works exactly)
If it is generated, then the bug is probably in the addon.

hmm... This specific mesh was not from an addon it was modeled in 2.8 from scratch.

It was created by hand in the editor (no custom script or anything fancy :) ).

Philipp Oeser (lichtwerk) renamed this task from Crash on collection visibility toggle to Crash on collection visibility toggle (corrupted mesh).Wed, Nov 20, 3:12 PM