Search Issue Tracker
Won't Fix
Votes
0
Found in
2019.1.0a12
2019.2
2019.3
2019.3.0b10
2020.1
Issue ID
1197656
Regression
Yes
PlayerPrefs.GetInt throws an exception when NativeArray<T> is initialized in a background thread
Steps to reproduce:
1. Open the project attached by the user
2. Open "NativeArrayTestScene"
3. Enter Play mode
4. Observe the console
Expected result: No exceptions or errors are thrown
Actual result: "UnityException: GetInt can only be called from the main thread." exception is thrown
Reproducible with: 2019.1.0a12, 2019.1.14f1, 2019.2.14f1, 2019.3.0f1, 2020.1.0a15
Not reproducible with: 2017.4.35f1, 2018.4.13f1, 2019.1.0a11
Note:
- The background thread has to be started before [RuntimeInitializeOnLoadMethod]s are called
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Job scheduling with batching is slow with dependencies and worker threads have poor utilization
- [HDRP] HDAdditionalLightData.RequestSubShadowMapRendering on directional lights breaks cascade shadows rendering
- Memory leaks when Instantiating Objects with SerializeReference
- Currently selected Action Map switches to the first Action Map in the list and it's first Action when editing the Binding Path of a newly created Action
- "F" default focusing Unity shortcut zooms out when the first time focusing the GameObject
Add comment