Search Issue Tracker
Fixed
Fixed in 1.3.X - Entities
Votes
0
Found in [Package]
1.2.3 - Entities
1.3.X - Entities
Issue ID
ECSB-1141
Regression
No
"NullReferenceException" errors are thrown when UnityObjectRef does not prevent asset from being garbage collected
Reproduction steps:
1. Open the attached “MissingAsset.zip” project
2. Open the “SampleScene” scene
3. Ensure that the “NewSubScene” in the Hierarchy is opened (the checkbox next to it is checked)
4. From the top menu click on Test > GC assets
5. Observe the Console
Expected result: No errors are thrown
Actual result: “NullReferenceException: Object reference not set to an instance of an object” errors are constantly thrown
Reproducible with: 1.2.1, 1.2.3 (2022.3.33f1, 6000.0.6f1)
Could not test with: 0.51.1-preview.21 (2021.3.39f1) (Could not resolve the Console errors)
Reproducible on: Windows 11
Not reproducible on: no other environment tested
Note: In the 2022.3.33f1 version the errors appear when hovering over the Scene or Game view
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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Resolution Note (fix version 1.3.X - Entities):
This will be fixed in the 1.3.0 release.