Search Issue Tracker
Fixed in 2019.1.1f1
Votes
0
Found in
2019.1.0a6
2019.1.0f1
Issue ID
1150416
Regression
Yes
[Android] Application crash on Adreno GPU's when executing method WarmupAllShaders() on application start
To reproduce:
1. Open attached project "Android9Crash.zip"
2. While in project, make sure GLES3 is set as primary GPU API
3. Build and run on Android device
Result: application crashes
Reproduced in: 2019.1.0f2
Not reproduced in: 2017.4.26f1, 2018.3.14f1, 2019.1.1f1, 2019.2.0a14, 2019.3.0a1
Note: earlier than 2019.1.0a6 releases produce build errors when testing 2019.1
Reproduced on devices:
VLNQA00015 Samsung Galaxy Note8 8.0.0 Snapdragon 835 MSM8998 Adreno (TM) 540 OpenGL ES 3.2 ce071717744900260c7e
VLNQA00218 Samsung Galaxy Note9 8.1.0 Snapdragon 845 SDM845 Adreno (TM) 630 OpenGL ES 3.2 24c16f24e60c7ece
VLNQA00005 Samsung Galaxy S7 7.0 Snapdragon 820 MSM8996 Adreno (TM) 530 OpenGL ES 3.2 533c0b26
VLNQA00173 Xiaomi Redmi 6 Pro 8.1.0 Snapdragon 625 MSM8953 Adreno (TM) 506 OpenGL ES 3.2 bc4bd3820205
Not reproduced on devices:
VLNQA00138 Huawei P20 Pro 8.1.0 HiSilicon Kirin 970 Mali-G72 OpenGL ES 3.2
VLNQA00231 Huawei HUAWEI Mate 20 Pro 9 HiSilicon Kirin 980 Mali-G76 OpenGL ES 3.2
VLNQA00224 Samsung Galaxy A5(2017) 8.0.0 Exynos 7 Octa 7880 Mali-T830 OpenGL ES 3.2
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Add comment