Page MenuHome

Blender closes while opening one of my particular scene file
Closed, InvalidPublic

Description

System Information
Operating system: Windows 10
Graphics card: NVidia GEFORCE GTX 1660 Ti

Blender Version
Broken: (example: 2.80, edbf15d3c044, master, 2018-11-28, as found on the splash screen)
Worked: (optional)

Short description of error
Blender closes while opening one of my particular scene file.

Exact steps for others to reproduce the error
I have a huge scene file as the link below. Blender keep on crashing while opening this particular scene file. I tried in different versions of Blender. And Tried to append the scene file / objects to a new scene file also. But still crashes. Please help me recovering this file, as we spent lot of time in doing the animations of this scene file.
http://e-animedia.fr/FREE/COULIDOOR/Kitchen_pART-03_968-2660.zip

Thanks in advance.
Regards,
Sivakumar Annamalai.

Event Timeline

# Blender 2.83 (sub 3), Commit date: 2020-02-15 17:44, Hash e0499387ca0a

# backtrace
41: BLI_system_backtrace - 0x7FF6D5C31450
40: sig_handle_crash_backtrace - 0x7FF6CEA3E250
39: sig_handle_crash - 0x7FF6CEA3DF10
38: windows_exception_handler - 0x7FF6CEA3E340
37: UnhandledExceptionFilter - 0x7FFA1DD9F4B0
36: memset - 0x7FFA1FF43000
35: _C_specific_handler - 0x7FFA1FF2C640
34: _chkstk - 0x7FFA1FF41100
33: RtlRaiseException - 0x7FFA1FF09EF0
32: KiUserExceptionDispatcher - 0x7FFA1FF3FE60
31: sub_v3_v3v3 - 0x7FF6CEBC1A90
30: split_loop_nor_fan_do - 0x7FF6CEBC0450
29: loop_split_worker_do - 0x7FF6CEBBC560
28: loop_split_worker - 0x7FF6CEBBC420
27: BLI_task_pool_work_and_wait - 0x7FF6D5CD97D0
26: BKE_mesh_normals_loop_split - 0x7FF6CEBB6F60
25: BKE_mesh_calc_normals_split_ex - 0x7FF6CEB7E500
24: BKE_mesh_calc_normals_split - 0x7FF6CEB7E490
23: mesh_calc_modifier_final_normals - 0x7FF6CECF8CF0
22: mesh_calc_modifiers - 0x7FF6CECF9040
21: mesh_build_data - 0x7FF6CECF87A0
20: makeDerivedMesh - 0x7FF6CECF84F0
19: BKE_object_handle_data_update - 0x7FF6CEE14A50
18: BKE_object_eval_uber_data - 0x7FF6CEE14840
17: std::_Invoker_functor::_Call<void (__cdecl*&)(Depsgraph *,Scene *,Object *),Depsgraph *,Scene * &,Object * &> - 0x7FF6D0289900
16: std::invoke<void (__cdecl*&)(Depsgraph *,Scene *,Object *),Depsgraph *,Scene * &,Object * &> - 0x7FF6D0298AE0
15: std::_Invoker_ret<std::_Unforced,0>::_Call<void (__cdecl*&)(Depsgraph *,Scene *,Object *),Depsgraph *,Scene * &,Object * &> - 0x7FF6D0289810
14: std::_Call_binder<std::_Unforced,0,1,2,void (__cdecl*)(Depsgraph *,Scene *,Object *),std::tuple<std::_Ph<1>,Scene *,Object *>,std::tuple<Depsgraph * &&> > - 0x7FF6D028C480
13: std::_Binder<std::_Unforced,void (__cdecl&)(Depsgraph *,Scene *,Object *),std::_Ph<1> const &,Scene * &,Object * &>::operator()<Depsgraph *> - 0x7FF6D02878F0
12: std::_Invoker_functor::_Call<std::_Binder<std::_Unforced,void (__cdecl&)(Depsgraph *,Scene *,Object *),std::_Ph<1> const &,Scene * &,Object * &> &,Depsgraph *> - 0x7FF6D028B450
11: std::invoke<std::_Binder<std::_Unforced,void (__cdecl&)(Depsgraph *,Scene *,Object *),std::_Ph<1> const &,Scene * &,Object * &> &,Depsgraph *> - 0x7FF6D02998B0
10: std::_Invoker_ret<void,1>::_Call<std::_Binder<std::_Unforced,void (__cdecl&)(Depsgraph *,Scene *,Object *),std::_Ph<1> const &,Scene * &,Object * &> &,Depsgraph *> - 0x7FF6D028B3B0
9: std::_Func_impl_no_alloc<std::_Binder<std::_Unforced,void (__cdecl&)(Depsgraph *,Scene *,Object *),std::_Ph<1> const &,Scene * &,Object * &>,void,Depsgraph *>::_Do_call - 0x7FF6D02A5290
8: std::_Func_class<void,Depsgraph *>::operator() - 0x7FF6D02D3170
7: DEG::`anonymous namespace'::evaluate_node - 0x7FF6D02D3B90
6: DEG::`anonymous namespace'::deg_task_run_func - 0x7FF6D02D38B0
5: handle_local_queue - 0x7FF6D5CDB1E0
4: task_scheduler_thread_run - 0x7FF6D5CDEA90
3: _ptw32_threadStart - 0x7FF6D5F25AA0
2: register_onexit_function - 0x7FF9D7BA5340
1: BaseThreadInitThunk - 0x7FFA1FDB7BC0
0: RtlUserThreadStart - 0x7FFA1FF0CEB0

There seem to be a couple of objects that are causing this error one is _582 appending that object will also cause a crash, other objects also cause a crash but I did not have time to isolate them.

@Sivakumar (sk916) until the bug is fixed to can re build the blend file by trying to isolate the other objects that cause the crash.

Aaron Carlisle (Blendify) changed the task status from Needs Triage to Confirmed.Feb 17 2020, 7:53 PM

Hi Aaron,
Thanks for checking. I understand, I will have to rework the entire animation. But can you suggest any action on how to protect the scene file from "not this issue to re-happen". Because I cannot afford if the issue occurs again after reworking the animations.

Thanks in advance.
Regards,
Siva

Bastien Montagne (mont29) claimed this task.

usual case of invalid mesh, appending just _582 mesh datablock, and calling .validate(verbose=True) on it gives you:

ERROR (bke.mesh): /home/guest/blender/src/source/blender/blenkernel/intern/mesh_validate.c:552 BKE_mesh_validate_arrays: 	Poly 37393 is invalid (loopstart: -1, totloop: 3)
ERROR (bke.mesh): /home/guest/blender/src/source/blender/blenkernel/intern/mesh_validate.c:733 BKE_mesh_validate_arrays: 	Loop 112179 is unused.
ERROR (bke.mesh): /home/guest/blender/src/source/blender/blenkernel/intern/mesh_validate.c:733 BKE_mesh_validate_arrays: 	Loop 112180 is unused.
ERROR (bke.mesh): /home/guest/blender/src/source/blender/blenkernel/intern/mesh_validate.c:733 BKE_mesh_validate_arrays: 	Loop 112181 is unused.

We cannot do much here, unless you can give us a way to reproduce such mesh corruption.

Note that once mesh has been validated, errors should be fixed, so you can probably fully save your work with a bit of data-block fiddling.