Search Issue Tracker
Fixed in 2018.3.X
Votes
0
Found in
2018.3.0a10
2018.3.0b3
Issue ID
1085675
Regression
Yes
Shader causes infinite "NullReferenceException" errors, even after deletion
Reproduction steps:
1. Open "MinimalRepro.zip" project
2. Look at the Console Window
Expected Result: No errors appear
Actual Result: "NullReferenceException" errors are infinitely spammed to the Console window
Fixed in: 2019.1.0a6, 2018.3.0b8
Reproduced with: 2019.1.0a3, 2018.3.0b4, 2018.3.0b1, 2018.3.0a11, 2018.3.0a10
Did not reproduce on: 2018.3.0a9, 2018.3.0a7, 2018.3.0a1, 2018.2.11f1, 2018.1.9f2, 2017.4.12f1
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Editor crashes when debugging a for loop
- Crash on UnityPlayer!profiling::ProfilerManager::DisposeProfilerRecorder+0xa when Player gets relaunched and exited after running for a long amount of time
- [Input system] When releasing one touch and pressing a second touch during a single frame, the second touch is not translated into UI event line OnPointerDown by the InputSystemUIInputModule
- URP Samples - multiple "Attempting to resolve render surface" and other errors appear when setting Quality pipeline asset
- OnDemandRendering.willCurrentFrameRender returns incorrect values in the Player when UnityEngine.Rendering.OnDemandRendering.renderFrameInterval is greater than 1
Add comment