Search Issue Tracker
Fixed in 2020.1.X
Fixed in 2019.2.X, 2019.3.X
Votes
2
Found in
2019.2.0b1
2019.2.2f1
Issue ID
1179631
Regression
Yes
Crash on SortByExecutionOrder after setting up font kerning values when PlayerPrefs.DeleteAll() is called in Start()
How to reproduce:
1. Open the "Level1" Scene in the "case_1179631repro.zip" Unity project (stored in ownCloud)
2. Enter Play Mode two or three times
3. Observe the crash
Expected result: an error is thrown which details the origin of the
Actual result:
Reproducible with: 2019.2.0b1, 2019.2.4f1
Not reproducible with: 2019.2.0a10, 2019.2.0a14
Note: not reproducible in versions earlier than 2019.2.0a10 and in streams 2019.3 and 2020.1 due to LWRP errors. Not reliably reproducible in versions earlier than 2019.2.0a14 and 2018.4 due to various package errors. Consistently reproduced on 2019.2.0b1 through 2019.2.4f1. The crash occurs when calling PlayerPrefs.DeleteAll() with the specific project setup.
Comments (1)
-
OleSviper
Sep 30, 2019 12:07
Probably not the exact same reason but we do have several crashes when building on Android in headless mode since updating to 2019.2. Sometimes it is enough to just retry, sometimes we can only fix it by deleting the Library-Folder...
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
- DisplayDialogComplex crashes with a long content string containg Cyrillic chars
- "Draw Additional Lights Shadowmap" calls increase when custom MaterialBlockProperty is used
- Crash on _platform_memmove when importing the "Dragon Crashers - URP 2D Sample Project" to a new 2D project
- "Shader is not supported on this GPU" warnings and and shaders are not loading when building the project for non-Chromium browsers
- [iOS][URP] The screen flickers and the "Execution of the command buffer was aborted due to an error during execution" error is thrown continuously
Resolution Note (fix version 2020.1):
Fixed in 2020.1.0a7
Resolution Note (fix version 2019.3):
Fixed in 2019.3.0b6
Resolution Note (fix version 2019.2):
Fixed in 2019.2.9f1.