I’ll make a copy as soon as it starts crashing again. Usually I get impatient and go through deleting things I don’t think I need until it stops crashing.
So the problem basically never went away. I have two new machines: a windows box with 32gb of memory (more than I had previously) and a Macbook pro. Both crash when editing materials, although the celshader project crashes far more frequently - about every second action inside of a material. You have to understand, this has crashed 10 times for me in 3 minutes and I’m just saving and editing and crashing, saving and editing and crashing over and over. We have to fix this.
Eric, I believe I’ve shared the project with you on Dropbox in the past - I’m working on a new copy so I’ll share that with you again. The material to edit is called “CelShader” and it’s in /Game/Shaders/CelShader/PostProcess.
MachineId:B089377643CEDC1B48EF58BD259BFA6C
EpicAccountId:0d22223890c14e53a7b95ab62128b47c
Unknown exception - code 00000001 (first/second chance not available)
"Fatal error: [File:D:\BuildFarm\buildmachine_++depot+UE4-Releases+4.9\Engine\Source\Runtime\ShaderCore\Private\ShaderParameters.cpp] [Line: 21]
Failure to bind no
UE4Editor_Core!FDebug::AssertFailed() [d:\buildfarm\buildmachine_++depot+ue4-releases+4.9\engine\source\runtime\core\private\misc\outputdevice.cpp:354]
Just going by the error, it’s nothing breaking, just something leading to a bad assert. Perhaps a race condition?
I think I might know the cause but I will need a copy of your project to test again. We try not to keep projects around after testing is completed.
Thank You -
Eric Ketchum
Since I may not be able to write back until Monday, try moving your project completely out of Dropbox folder into any other folder and do not allow Dropbox to sync this new folder. Does the crash still occur after doing this?
Thank You Again -
Eric Ketchum
Ah, interesting idea. I’ll give that a go now, although I hate losing a stage in my backup process.
Edit: yep, that feels a lot more stable. You seem to have nailed it.
DROPBOX IS BAD EVERYONE
Hello -
I wanted to give a more definitive answer to this report. It does appear that syncing a project with Dropbox will cause a crash when your Editor is attempting to write to the Intermediate folder, which usually happens when compiling shaders, opening maps etc.
It does look like in UE-17227 which was fixed in time for the 4.10 release, an attempt to harden the engine against this type of crash was put in place. A brief attempt with Antidamage’s project was made in 4.10 using Dropbox and did not experience a crash. This will work for a large percentage of people with this issue, but may not fix every single one.
My biggest suggestion is not to use Cloud storage (Dropbox, Google Drive, OneDrive, etc.) directly with your whole project directory. If you do make sure that you manually control syncing and do not try to sync while also working on the same project files.
Thank You
Eric Ketchum