Page MenuHome

Crash on file open
Closed, DuplicatePublic


System Information
Operating system: macos 10.14.6 (18G87)
Graphics card:

  • Radeon Pro Vega 20 4 GB
  • Intel UHD Graphics 630 1536 MB

Blender Version

  • 2.80 ,official release (2019-07-30)
  • 2.81.0 189aa32a3ac0, 2019-08-21

Short description of error
First Crash happened while working on Action Animations.
File won't open any longer (crashes everytime)

Exact steps for others to reproduce the error

  • low poly mesh with Low res UV, (texture and material node setup)
  • eevee
  • Armature
  • two open windows (main + side), side has 6 3d views, main has 3d view, timeline and dropsheet (action editor) open
  • multiple set actions

Crashed while trying to set locRotScale on bones



Event Timeline

@Samer Muar (ardicilliq) Umm! By following same steps you can reproduce the error again?
This file is crashing...

@Abid Maqbool (cto.abid) it's the second time it happened with this project... the first time it happened I managed to reopen it by recovering the last session, but this time I accidentally clicked on another project first and I can't open the file now.... I tried to open it on windows as well (2.81 2019-08-22)....
I can try to reproduce it with a new project.... but I really hope to save this one... :(

Dalai Felinto (dfelinto) lowered the priority of this task from Needs Triage by Developer to Needs Information from User.Aug 22 2019, 5:19 PM

It certainly help a lot if you can reproduce from scratch. Regardless, was this file made entirely with 2.80 official release?

This seems like a bug in the derived mesh code generation of normals. Maybe a race condition. It breaks consistently:

Thread 7 "blender" received signal SIGSEGV, Segmentation fault.
#0  mesh_calc_normals_poly_prepare_cb (userdata=0x7fff9a8b74b0, pidx=1024, UNUSED_tls=0x7fff9c8bc4d0) at //source/blender/blenkernel/intern/mesh_evaluate.c:255

Full thread 7 backtrace: P1080
And from other threads: P1079

Or even better, when running with -t 1 --debug-depsgraph-no-threads: P1081

I'm currently trying to repro from scratch... although haven't been able to yet...
The project was originally created with one of the 2.8 beta version... Unfortunately I can't remember which one and I already deleted It (because of the first crash I described above) I pretty sure it was a version from 2019-03-30~
after the first crash it occurred to be that there might be newer versions so I then downloaded the official 2.80...
The model wasn't started from scratch though ... It's from a fbx file (adding file to comment:

and here is the texture it's using:

If the bad file was created with a beta version and you cannot reproduce with 2.80 and on there may be nothing we can do. We are to remove DerivedMesh entirely maybe that will help your case.
@Campbell Barton (campbellbarton) any 2 cents here?

@Dalai Felinto (dfelinto) So there is no way newer release can fix this file or at least make it open so I can somehow export the animations?
Is it possible to somehow get the beta version and try it there? because the crash happened in the official version (the crash that happened in the official version is the one the corrupted it)

Can I manually remove DerivedMesh if I download the source code? can I compile the a local version and fix it there? or somehow comment the crashing code so I can at least save the contents of the file?

Animations are fine, the issue is somewhere in the mesh. So you can just open a new file and Append the actions from your problematic file.
Here, your FBX imported with the Actions appended from your original .blend:

@Dalai Felinto (dfelinto) Omg I can't thank you enough! Im already knees deep in trying to debug the whole thing, I've already built the project and everything...
So the mesh is problematic?
Should I fix something there?
Do you think it might happen again with this mesh?
And how can I export the animations like you did in case in happens again?

Thanks a lot of the effort again... really appreciate it...

Since you will now work from the official, stable 2.80 from scratch, I really hope you don't run into any issues. If you do, though, we will be more able to tackle it as a bug.

So the mesh is problematic?

Yes. It seems corrupted.

Should I fix something there?

Not really, just carry on using Blender.

Do you think it might happen again with this mesh?

No idea. I hope it does so we can find and fix the bug, if there is one ;)

And how can I export the animations like you did in case in happens again?

I didn't export. I imported them in the other file. Look at the Blender manual on Appending datablocks from other .blend files.

Googled How to do it :D
Should work for me.. I'll just have to save often so I won't lose too much progress if it happens again (hopefully it won't with a new created project)

So you can close the ticket I guess, if you say it's lost anyways and I got my animations :D.