Search Issue Tracker
By Design
Votes
0
Found in
2018.4
2018.4.17f1
2019.3
2020.1
2020.2
Issue ID
1243721
Regression
No
[Critical] Unity crashes when upgrading a project with a broken shader
Reproduction steps:
1. Open the attached project ("1243721.zip") (might crash on opening)
2. Open "Mandelbrot" Scene
3. Select "Raw Image" GameObject so it would draw it in the Inspector
Reproducible with: 2018.4.23f1, 2019.3.14f1, 2020.1.0b9, 2020.2.0a11
Notes:
- The source of the issue seems to be an error in a shader created by the user
- The project opens up without an issue and only freezes and artifacts when resizing in 2018.4, but when trying to upgrade the project to a newer version, it crashes on upgrading
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Some UXML Template Asset foldouts appear enabled when all fields inside are disabled
- URP Terrain Demo crash on burst_signal_handler after Generating lighting
- Project window button icons are poorly visible and their shades differ in Light theme
- GC.Alloc called by HDRenderPipeline.LensFlareMergeOcclusionDataDrivenPass() when playing the default HDRP Sample Template project
- Automatic LOD fails and SRP Batcher incompatibility occurs when using spline-based quad-topology meshes
Resolution Note (2020.2.X):
The shader has a loop that is controlled by the material. The number of iterations is set to 10^14.
Manually editing the material and setting a sane number or iterations solves the issue.