Great to hear you’re using OctaneX.
I’m also planning to use it (finally get the GPU to work!), but I thought I’d wait for the free (for 1 year) version in fall.
Is there a reason you’re not using OctaneX with 2.83?
Is it not ready for it?
2.90 - The files which crash, when you’re opening them - do those files always crash or can you open them sometimes and sometimes not?
It’s my mistake. It is 2.83 of course. Corrected.
I have Octane X monthly subscription for now. I have waited long enough.
2.90 - sometimes it crashes at first time I open the .blend. Next time it’s ok.
Yes I’m getting this too in 2.9 OSX. Once it corrupts I have to track a down a collection which seems to be the culprit. No matter what I do that collection and the objects in it are toast. Sucks when it’s the collection holding a character with a months worth of animation.
What’s most scary is that my autosave of the corresponding file becomes corrupt too.
Had this happen in 2.82 alpha a few times and have to use Bootcamp 2.9 for now. I’m needing EEVEE motion blur for my project and can’t risk it. Lately, most of the time I’m in Bootcamp just for Blender anyways.
Almost lost/start at a super early version of a really big file I’m working on. Luckily I found a day old version on my “transfer to Windows” hard drive. Maybe I need to turn blend1 saves back on.
Had a knotted stomach for a good twenty minutes.
Have you reported these issue to Blender?
I’m on Mac Catalina, using 2.83. I’ve had no problems.
Update with my particular instance of this problem.
I had to append every object 1 by 1 into a new scene and by doing that I realized 2 of the objects were causing the crash at startup (there was nothing particularly different or unique about them either). When I would attempt to append those specific ones it would once again crash so it was a pain but I managed to weed them out through the method.
Additionally, I’ve noticed the trend in recreating the issue is when Blender crashes while in the middle of saving. I thought it was due to me rendering the scene, but I have the nasty habit of clicking “Save” then immediately clicking “Render” prior to the save completing, which would cause the crash then corrupt the file. Since then, I’ve waited until the save fully takes before rendering and I haven’t seen the issue.
I have not reported it, yet. First I wanted to hear if other users have similar issues.
Did anyone else report it?
Would be very interesting to know…
Oh, I totally understand that. I was also waiting for OctaneX for several month.
Just to get seduced to wait even longer.
How is your experience so far? Is OctaneX production ready?
Thanks Cmubrew for the detailed description.
I think this is very similar / identical to my problem.
I have to admit that I’m also guilty of pressing render very quickly after saving. 
So far, in other versions than 2.90, that never caused a problem, though.
I’ve only just started learning Octane X, so it’s a little too early for me to judge if it’s production ready. However at this point it looks fast, rock stable and displacement is awesome 
. No crash at all.
Sometimes the problem is Octane Server but there is a new release PR1.1 on the way so I hope OTOY will fix this.
To be honest I will miss Cycles a bit…
So, after having a lot of issues with corrupted collections or objects over and over again, I reported it.
Unfortunately I can not reproduce the error, as it seems to happen randomly. And even worse it happens on collections and objects which are muted. Every now and then, when I try to activate a muted collection Blender instantly crashes. Checking the file more closely I usually notice that several collections (or/and objects) in that file have been corrupted. But it only happens to collections which are muted, I think. And that’s why I only notice the issues a while after it actually happens. The collections I’m currently working on never have a problem. But secretly in the background Blender must corrupt muted files, which seems super weird. And it made me save a new project file every 15min which is absurd. My project numbers are in the hundreds now.
So all I could do when reporting the issue was to share a file with a corrupted collection. The devs found corrupted meshes in it, but will not investigate as I can not reproduce the steps leading up to the issue. Unfortunately.
This basically turns all Blender versions newer then 2.82 unusable for me!
Which brings me to the question, if I can live with that and am ready to accept to be stuck with a stranded software?
So if anybody else who had this issue has found a workaround, or noticed that a latest version does not have the issue any more - I would be super thankful to get to know about it.
Also any other user who has this issue reporting it here, might help to get a bit closer to track it down, or show the importance of this issue.
Hmm…maybe I will have to use bootcamp as well. Seems to be the only solution to be able to use recent Blender versions for me.
May I ask how the performance of Blender in Bootcamp is compared to the performance of Blender on MacOS?
I’ve had more crashes in one day than in a whole year of using blender daily. When 2.90 was in Beta I had a few instances of files being corrupted but no crashing.
Just now I experienced unticking a collection then reopening the file and that collection was no longer a child of the Scene Collection. I had to go into “blender file” mode of outliner and find it and then make a 2nd outline to allow me to drag it from “blender file” mode over to “view layer” mode under the “Scene Collection”
Thanks for your post Thinsoldier.
Are you on MacOS Catalina?
And didn’t you experience any corrupted files with 2.90 RC anymore?
Early in 2.90 I had corrupt files. Betas around mid August were fine. Final release version is nearly unusable 
I’m on Mojave 10.14.5
Bugger. I hoped they would sort these issues for the final release version.
It’s such a shame - Blender used to be extremely stable before 2.83…
Honestly I did not dare to use any version of 2.90 anymore, since I lost too much time rebuilding corrupted projects on 2.83 and 2.90 already.
Bootcamp runs perfectly fine. 2.81 to 2.82 animation playback in the viewport was considerably slower with the Windows version compared to OSX, but that seems to be resolved from 2.83 and on.
EEVEE will render faster for you on Bootcamped Windows, at least for me. Cycles CPU renders are marginally faster with OSX. Maybe something to do with OSX native use of the CPU compared with the Bootcamped version?
You can dedicate an external SSD for Blend files if you prefer to cut and composite in OSX like I do. Really, the only hassle is just rebooting the system, which isn’t really.
To be honest, I’m working so much in Blender that I have my start-up drive set to Bootcamp.
One thing is that eeVee openGL under macos lacks some tools as it seems because volumetric clouds do not work on macOS!
The new Blender blunder is pretty hefty with 2.9.
I am not sure how metal api will be introduced if at all.
Seems to me that the time to run mainly bootcamp on my macs does make more sense lol …
I think the plan is vulkan first and then pray there is a good vulkan to metal bridge library they can take advantage of instead of having to write metal api code themselves
Oh, I thought that had been added with 2.90?
It’s the one thing I missed most in the Mac version of Blender.
Praying we are! 
On my 24” 2014 ima. It works fine.
Must be the older Xeon chips