Search Issue Tracker
Won't Fix
Won't Fix in 1.0.X
Votes
0
Found in [Package]
1.0.0
Issue ID
ECSB-182
Regression
No
An exception is thrown when calling GetSingleton<>() in specific method constellation
Reproduction steps:
1. Open the “My project” Project
2. Open the “Assets/Scenes/SampleScene.unity” Scene
3. Open the “Assets/Scripts/AnySystem.cs” Script and observe lines 29-30
4. Observe the Console Window
Expected result: No error is displayed in the Console Window
Actual result: An error is displayed in the Console WIndow
Reproducible with: 0.51.1-preview.32 (2021.3.17f1)
Could not test with:
- 0.51.1-preview.21 (2020.3.44f1 (error CS0619: 'FixedString128' is obsolete: 'Renamed to FixedString128Bytes (UnityUpgradable) -> FixedString128Bytes'))
- 0.17.0-preview.42 (2021.3.17f1 (error CS8377: The type 'U' must be a non-nullable value type, along with all fields at any level of nesting, in order to use it as parameter 'T' in the generic type or method 'NativeList<T>'))
- 1.0.0-pre.15 (2023.1.0a26 various Library/PackageCache/com.unity.collections@2.1.0-pre.6 errors)
Reproduced on: Intel MacOS 13.1
Notes:
- if you comment the line 29 and call and return it through a separate method (uncomment line 30), the issue does not occur.
- The issue does not occur in the OnUpdate() function
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
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
Resolution Note:
There are no fixes planned for this Bug
Resolution Note (1.0.X):
There are no fixes planned for this Bug