Search Issue Tracker
Fixed in 2020.2.X
Votes
0
Found in
2020.1
2020.2
2020.2.0a15
Issue ID
1259525
Regression
No
[Android][GLES3] Crash on Samsung Galaxy J5 after launching gfx tests
How to reproduce:
1. Open the attached project
2. Make sure platform set to Android
3. Go to TestRunner window (Window->General->TestRunner)
4. Run PlayMode tests by clicking "Run all in player(Android)"
5. Observe the device
Expected results: Tests are running
Actual results: Device crashes
Reproducible with: 2020.1.0b13, 2020.2.0a15
Mobile devices
Reproducible with:
VLNQA00111, Samsung Galaxy J5(2016) (SM-J510FN), Android 7.1.1, CPU: Snapdragon 410 MSM8916, GPU: Adreno (TM) 306
No repro:
VLNQA00287, Motorola moto g(7) power (moto g(7) power), Android 9, CPU: Snapdragon 625 MSM8953, GPU: Adreno (TM) 506
VLNQA00216, Razer Phone 2 (Phone 2), Android 8.1.0, CPU: Snapdragon 845 SDM845, GPU: Adreno (TM) 630
VLNQA00269, Samsung Galaxy S10e (SM-G970F), Android 9, CPU: Exynos 9 9820, GPU: Mali-G76
VLNQA00090, Samsung Galaxy S8 (SM-G950U), Android 7.0, CPU: Snapdragon 835 MSM8998, GPU: Adreno (TM) 540
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
- [Linux] Mouse position is incorrect when playing build on a multiple monitor setup in full screen mode
- PlayerSettings.asset displays incorrect appleEnableAutomaticSigning value
- [Linux] Silent crash on TLSAllocator<(AllocatorMode)0>::ThreadInitialize(unsigned long, char const*) when restarting after setting Graphics API to Vulkan
- AssetBundle allocates more memory when loading it a second time
- Box Collider outlines are not affected in the Game view when changing the 3D Icons option
Resolution Note (fix version 2020.2):
Samsung Galaxy J5 does not support compute.