Its not exactly a bug? but whenever I just open a material a bunch of shadercompileworkers spawn in my activity monitor and my fans scream. If I wait long enough UE4 will usually crash or hard freeze my machine which is way worse. Also they take over my processors. Hitting save on a material takes over 100% of my CPU time (it will even say 102% which I don't understand...). Why does it go crazy just opening a material ? Also saving a material is very slow compared to all other saves. Is there something I can do to calm them down? I have turned off live update and statistics but I still have to save.
I am using UE4.14.1 ( it did the same in previous versions) iMac Retina 4.0 ghz i7 and another at home which is 3. something with Sierra .
I feel like if this problem is fixed UE4 will run much cleaner and be more stable on a Mac. Right now I save allll the time due to random crashes. Not sure if they are related.
asked Dec 09 '16 at 03:30 PM in Using UE4
So I had a peer run a test on his Mac with very similar specs to your machine, and he saw some spikes in CPU usage when shaders were compiling, but once they completed compiling, the editor's performance returned to normal without any crashes or freezing.
Unfortunately, unless we can reproduce this issue internally, we cannot move forward with the bug reporting process. I would be sure you are not running anything in the background while you are compiling shaders.
With all of this said, we do have some documentation on being able to modify the Shader Cache so you can optimize shader compilation.
Let me know if you have additional questions.
answered Dec 12 '16 at 09:14 PM
Follow this question
Once you sign in you will be able to subscribe for any updates here