Search Issue Tracker
Won't Fix
Votes
0
Found in
2021.3.36f1
Issue ID
UUM-67374
Regression
No
"SaveGameStateToFileTask()" throws Assertion errors on changing the Game State when variables of type "Item" are Serialized in GameManager
How to reproduce:
1. Open the user-attached project “Test”
2. Open the “Main Scene” scene and enter the Play Mode
3. Click one time in the Game view to enter the game menu
4. Click on any hexagon with the picture
5. Observe the results
Expected results: The Game State changes without errors
Actual results: The Game State changes with hundreds of Assertion errors
Reproducible with: 2021.3.36f1
Not reproducible with: 2022.3.22f1
Can’t test with: 2023.2.15f1, 6000.0.0b13 (Unfixable compilation errors)
Reproducible on: Windows 11 Pro
Not reproducible on: No other environment tested
Notes:
-The messages don’t affect the functionality
-The messages are not spammed when “[NonSerialized]” is added to all public variables of type “Item” in GameManager
-Can’t find the fixed version due to complexity in upgrading and downgrading the project
Full error:
Assertion failed on expression: 'CurrentThreadIsMainThread()'
UnityEngine.JsonUtility:ToJson (object)
GameManager:SaveGamestateToFileTask () (at Assets/Scripts/GameManager.cs:2134)
GameManager:<SaveGamestate>b__203_0 () (at Assets/Scripts/GameManager.cs:2074)
System.Threading._ThreadPoolWaitCallback:PerformWaitCallback ()
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
- VFX Graph Memory leak when calling the ClearPropertyBinders and AddRemoveVFXProperty
- Entering "Configure Avatar" inside the Inspector locks it
- [Render Graph Viewer] Resource list icons cropped and in inconsistent positions
- Scene View with Debug Draw Mode enabled is gray when GPU Resident Drawer is enabled
- The UI is not visible when resizing out of focus built Player window with Application.runInBackground set to false
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.