Search Issue Tracker
Fixed in 2021.2.X
Fixed in 2019.4.X, 2020.2.X, 2021.1.X
Votes
0
Found in
2019.4
2019.4.9f1
2021.1
Issue ID
1293534
Regression
No
Crash on RaiseException when calling JsonUtility.FromJson with a corrupted json file
Reproduction steps:
1. Open the user's attached project
2. Go to Window > General > Test Runner
3. Double-click on either of the two tests
-- observe crash
Reproducible with: 2019.4.15f1, 2020.1.15f1, 2020.2.0b13, 2021.1.0a7
Could not test with: 2018.4.29f1 (errors)
Note:
-In 2019.4 and 2020.1 the editor crashes without the Crash Handler and no stack trace is printed in the Editor log
-User mentioned that the two different json files that are called in the tests have been generated by a corrupted JsonUtility output
-
miloszecket
Apr 22, 2021 18:41
AND 2021.2.0a14
-
miloszecket
Apr 22, 2021 05:29
i should specify: this is still happening in 2021.1.3f1
-
miloszecket
Apr 22, 2021 05:18
not fixed, actually
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
- Crash on mecanim::SetValueWeight when switching the AnimationMixerPlayable connection with Animator's UpdateMode set to "Animate Physics"
- The "StringComparer.InvariantCultureIgnoreCase.GetHashCode()" returns different Hash Codes for the same word with the only difference being case sensitivity in WebGL
- 2D Light Textures show the lights of any 'blend style' index higher than theirs (if present) when they aren't visible by the Camera using Render Graph
- [SpeedTree] Wireframe mode not rendering correctly ST assets
- Light2D affecting only the Default Sorting Layer will also affect any Custom Lit Sprite not on that Layer when using Render Graph
Resolution Note (fix version 2021.2):
Fixed crash that would occur when we would attempt to deserialize and new a class that is not fully instantiated.
Fixed in 2021.2.0a2.
Resolution Note (fix version 2021.1):
Fixed in 2021.1.0b6
Resolution Note (fix version 2020.2):
Fixed in 2020.2.5f1
Resolution Note (fix version 2019.4):
Fixed in 2019.4.20f1