Search Issue Tracker
Fixed in 5.3.0
Votes
0
Found in
5.1.2f1
Issue ID
719574
Regression
Yes
[Crash] Crash in ShaderLab::IntShader::GetTag, legacy Shaders used in Editor crash Unity on scene loading
How to reproduce:
1. Import the attached Unity package "ShaderCrash719574" to a new project
2. Open CherryPop scene
3. Unity will crash while loading
4. If you import the package to Unity 5.0, everything works good and you can see legacy shader in the scene which is used in scripts
Crash was in ShaderLab::IntShader::GetTag
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
Add comment