Search Issue Tracker
Fixed
Fixed in 2022.3.46f1, 6000.0.18f1, 7000.0.0a1
Votes
1
Found in
2022.3.39f1
6000.0.12f1
7000.0.0a1
Issue ID
UUM-76654
Regression
Yes
NullReferenceException is thrown and unnecessary Re-Binding of ListView Elements when modifying List Elements in custom Inspector with Generic SerializedProperty
Reproduction steps:
1. Open the attached “BugRepro” project
2. Open the “Assets/Scenes/SampleScene.unity” Scene
3. Click on the "CarSettingsManager" GameObject in the Hierarchy view
4. In the Inspector view, modify any of the fields in the "Car Settings List"
5. Observe the Console window
Expected result: No errors are thrown, and list elements remain bound without unnecessary un-binding and re-binding upon modification
Actual result: “NullReferenceException: Object reference not set to an instance of an object” error is thrown and list elements are unnecessarily un-bound and re-bound with each modification
Reproducible with: 2022.3.28f1, 2022.3.39f1
Not reproducible with: 2022.3.27f1, 6000.0.12f1
Couldn't test with: 2021.3.40f1 (No GUI Implemented)
Reproducible on: Windows 11
Not reproducible on: No other environment tested
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
- Select Preset "None" icon changes after switching tabs
- [Android] Crash when using xxHash3 and targeting the ARMv7 Architecture with IL2CPP Scripting Backend
- GameObject reference in a Script Component becomes missing when unpacking a variant of another Prefab variant
- Project Settings vertical separator position is not synchronized with the mouse position when dragging it horizontally
- Crash on PhysicsDebugDraw::SelectFiltering::Update when entering play mode with Physics Debug window docked and unfocused
chadfranklin47
Jul 24, 2024 10:01
I want to add that the primary issue here is not the NullReferenceException itself, but the unbinding and re-binding of ListView elements unnecessarily on every value change. It is here that the NullReferenceException occurs, but this should not be happening in the first place.