Blender 2.91 and 2.92 crashes

hi @mib2berlin :slight_smile:

This is my problem… symplifying… i got linked objects more than 200 lights, 150+ objects, 10+ materials, etc…
My project blend is 100MB and i got more than 400MB of textures. Nothing blender devs can be interrested in for debugging.
When i delete some objects, things seem to run properly.
Maybe it comes from one corrupted mesh ? but wich one ?

I separated my blend file from my unity project and tried to reproduce the crash…
And finally after some few changes, i’m totally unable to load this file !
30+ unsuccessfull tryouts.
But the question ( as there are some unfindable linked files ) is it representative from the real problem ?
I’d say no as the crashlog says something else than before:
4th.txt (30.5 KB)

However the crash still exists and also seems to come from BMesh libs…

Finally i compressed the bugged file but am not hot at sending this whole work in nature :confused:
It is not simplified at all and represent thousands of work hours.

I gonna try to dig further^^

Understand, did you try to open the file in 2.93 Beta?
There was hundreds of bus fixed since 2.92, may be a workaround.

Cheers, mib

Start by disabling all non standard addons !

this is a pretty goo idea ! :rofl:
Am so stuck on this that i didn’t even think about it…

The time to download it and i give it a try.

I got some few strange info though.

when dbl-clicking on the .blend file in windows, blender launches, try to open the file and crashes.
However, i was able to load the file from the recent files of the splash… :confused:
I changed some thingies and saved and now dbl-click on the file in windows still crashes and opening from the recent files list of the splash also crashes…
however, i’m still able to load the file from the file menu !

Meaning those 3 different loading ways give all different results.

I really suspect my file is kinda corrupted ( wich should not occur if blender were okay at data handling ) and maybe missing libraries or broken links bother it a lot ( wich should enventually fuck-up the scene but not crash the app IMHO )

@stephen_leger oh yes this is also a pretty good idea :slight_smile:
I try this right away…

EDIT: I disabled the 2 addons i used: magic_uv & forgotten tools and nothing changed :confused:
It appears addons are innocent :wink:

still downloading…

back there with some more info though.

On this selected mesh:


coming from one of my libs, i had an action made of one keyframe that i found on the moved file with broken links… i deleted the action in the original file, and deleted and reloaded the linked object in my final baking file.

After some tryouts, bothering the file ( select, bake, stop bake, stop, select, bake… ) it seems not to crash anymore…

10 minutes passed since i started writing <

OKAY :japanese_goblin: am totally lost !!!

The file that 100% crashed (with more then 50 unsuccessfull tryouts ) at load now loads without a crash !
my wife passed-by, my cat scratched its right ear and voilà !

:partying_face:

now it’s for me time to go to bed with a temesta…

I experienced things like this in the past with a corrupted memory on my computer. But the crashes and bugs were really random and not always crashed on the same function !

well…
I gonna keep beeing vigilant and dig on this further in the near future and i’ll post here news about this strange behaviour…

In the meanwhile, happy blending ! :slight_smile:

1 Like

News on this case.

The problem comes obviously from my file as it also crashes on another computer and also on 2.93alpha.

After investigating, i noticed this comes from the basilica ( the big green building on the previous post.

As the basilica is a linked object am not sure though wether the basilica source blend is corrupted ( even if i had no problem at all with it ) or if it’s the link and changes that fucked it up.

Now i deleted the basilica and saved/reloaded 3 times the file to kill orphan data and appended it again.

now load/bake seems to run properly.
I just have to change the materials for each of the basilica element and i’ll see wether the problem occurs again.
Am not event sure i can reproduce it and i’ll never know why it was corrupted :confused:

Some more news soon.

Happy blending !

+1

I’ve been getting this issue quite a lot and totally random, sometimes after 10min, sometimes after 1h.

I’m using Geforce 2070 Super (v461.92) + Intel 4770K + Blender v2.92.0.

Google shows there are a lot of people with this issue and Blender devs seem clueless. It could be something on Nvidia’s driver though.

Going to try 2.93 Alpha.

1 Like

Some more people are reporting the same. The Devs I am sure are taking this seriously as it seems to touch Nvidia graphic cards. Here is the bug report page which is active :slight_smile:

https://developer.blender.org/T85977

For now I would recommend everyone who are working on large projects to use 2.83 LTS version. I have no issue with it. Hoping they resolve this soon.

1 Like

That’s nice. As a workaround I’m avoiding whenever possible using viewport shading and use eevee instead. No crashes so far.