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
- Crash on std::__1::__tree_const_iterator when opening the Build Profiles window in a specific project
- Sub-State machine “breadcrumb trail” doesn’t fit in the window if there’s too many Sub-State machines
- Lighting artifacts in Scene when baking box lights
- [Ubuntu] Rendering Debugger's "Material Texture Slot" dropdown has an enormous empty space
- Empty space at the end of the Animator Parameters section when scrolling down
Add comment