Search Issue Tracker
Won't Fix
Votes
0
Found in [Package]
1.8.4
Issue ID
BUR-2425
Regression
No
Null references are not recognized when Burst Compiling
Reproduction steps:
1. Open the attached “ASDQWE” project
2. Open the “Asset/Scenes/SampleScene.unity” Scene
3. Enter the Play Mode
4. Observe the Console Window
Expected result: No error is thrown
Actual result: Two slightly different “IsNotNullRef: This code should not be called. Null reference not recognized." logs are thrown
Reproducible with: 1.8.4 (2022.3.2f1)
Could not test with: 1.6.6 (2021.3.27f1), 1.7.4 (2021.3.27f1), 1.8.4 (2023.1.0f1, 2023.2.0a18) (Requires entities 1.X package)
Reproducible on: Intel MacOS 13.4
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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
Resolution Note:
Not a bug, as explained in this forum post: https://forum.unity.com/threads/in-43029-burst-compiled-code-cannot-recognize-null-references.1444897/#post-9060079