Page MenuHome

Segmentation 11 fault on macOS Big Sur
Closed, ArchivedPublic


System Information
Operating system: Darwin-20.1.0-x86_64-i386-64bit 64 Bits
Graphics card: AMD Radeon Pro 5500M OpenGL Engine ATI Technologies Inc. 4.1 ATI-4.0.47

Blender Version
Broken: version: 2.91.0, branch: master, commit date: 2020-11-25 08:34, hash: rB0f45cab862b8
Worked: (newest version of Blender that worked as expected)

Short description of error
I'm trying to create many scenes for my blender project, but when I tried to open up "Scene 2 shot 2 close up", it just crashes. It's similar to my last project's crash too, it both says segmentation fault 11. I would love to have this problem fixed, and also if you guys could send me back a debugged version, thank you, I worked really hard on this project.

Exact steps for others to reproduce the error

I've uploaded the crash information plus the blender file

Related Objects

Event Timeline

The object cloth.003 causes mesh problems. Not sure what caused it, but mv_2->co in sub_v3_v3v3(vec_org, mv_2->co, mv_pivot->co); is garbage.

Quick solution: simply delete this object in the outliner (do not open the scene - just right click the object and delete it), recreate this mesh and continue working on your project.

Stack trace:

blender!sub_v3_v3v3 (/Users/*/devel/blender-git/blender/source/blender/blenlib/intern/math_vector_inline.c:493)
blender!split_loop_nor_fan_do (/Users/*/devel/blender-git/blender/source/blender/blenkernel/intern/mesh_evaluate.c:1158)
blender!loop_split_worker_do (/Users/*/devel/blender-git/blender/source/blender/blenkernel/intern/mesh_evaluate.c:1307)
blender!loop_split_worker (/Users/*/devel/blender-git/blender/source/blender/blenkernel/intern/mesh_evaluate.c:1335)
blender!Task::operator()() const::'lambda'()::operator()() const (/Users/*/devel/blender-git/blender/source/blender/blenlib/intern/

ok got it, thank you so much,

It seems like the mesh got corrupted somehow. If I validate the mesh data in the Scene 2 shot 2 close up scene it returns false for the following meshes.

name: cloth.003 valid: False
name: ipad.003 valid: False
name: Plane.001 valid: False

So this is not a bug. As @Jean First (robbott) mentioned, you can delete the objects to get it working again or try and extract the mesh using python, then delete the objects and reconstruct them from scratch with the saved data. Closing.