Search Issue Tracker
Fixed
Fixed in 2023.1.8f1, 2023.2.0a21
Votes
0
Found in
2023.1.0b18
2023.2.0a17
Issue ID
UUM-36754
Regression
Yes
NullReferenceException when selecting Terrain prefab in Project browser
Reproduction steps:
1. Open the attached project “repro_terrainIssue“
2. Select the “Terrain“ prefab in the Project browser
Expected result: No errors appear in Console
Actual result: There is an error in Console: NullReferenceException: Object reference not set to an instance of an object
Reproduced with: 2023.1.0a19, 2023.1.0b18, 2023.2.0a17
Not reproduced with: 2020.3.47f1, 2021.3.26f1, 2022.2.19f1, 2023.1.0a18
Reproduced with: macOS 13.0.2 (Intel), macOS 12.6.1 M1 (user reported)
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
- “Screen position out of view frustum...” errors are thrown when zooming out in the Scene view after creating UI GameObject
- CurveTexture is not being released when unloading AssetBundle containing a Scene with ColorCurves post-processing component in Global Volume
- Crash on ExtractActiveCasterInfo when navigating the scene view in a project with specific lighting data
- Build Profile name increments when numeric suffix is removed from duplicate Profile name
- "Unrecognized block header in profiler data file, stopping deserialization" error is shown and no more profiler data is recorded when the Player is connected and profiler recording is enabled/disabled few times
Resolution Note (fix version 2023.2.0a21):
There were some circumstances in which selecting a prefab terrain would cause Unity to try and access some uninitialized data. This error has been fixed.
Resolution Note (fix version 2023.1.8f1):
Backported from the 2023.2 fix.