Operating system: Darwin-18.6.0-x86_64-i386-64bit 64 Bits
Graphics card: Intel Iris Pro OpenGL Engine Intel Inc. 4.1 INTEL-12.9.22
Broken: version: 2.80 (sub 74), branch: master, commit date: 2019-07-11 13:50, hash: rB06312c6d2db8
Short description of error
[Need to create a safeguard to allowing shaders from Blender internal to avoid crashing when enabling viewport shading.]
Exact steps for others to reproduce the error
[Sometimes when opening an old file; or from a free online resource, a file containing an older shader for what I assume was Blender internal; causes the program to crash when enabling viewport shading with EEVEE. My thought is that there should be a way to either warn of the conflict before entering the shading; perhaps with a couple options to mitigate the problem:
Option 1) Allow Blender to try and replicate the desired shader using EEVEE Nodes; knowing it may still need some tuning later.
Option 2) Allow Blender to pinpoint the exact source of the conflict and allow the user to not it; and delete the node if there are nodes present.
Option 3) Allow the user to discard any Shaders altogether that will cause a crash.
I have attached a simple file with a chair I downloaded from Blendkit; which demonstrates this undesirable behavior.]