Search Issue Tracker
Fixed in 2017.2.X
Votes
0
Found in
5.5.2p2
Issue ID
896001
Regression
No
[Android] Crash in particle system on Vivante GC1000
How to reproduce:
1. Open the attached project "ReproCrashTab3_2017-04-06.7z (4.5 MB) "
2. Build and run "TestSceneCrash" scene on Samsung Galaxy Tab 3 Lite
Result: application crashes after few seconds
DUT(reproducible):
Samsung Galaxy Tab 3 Lite 7.0 WiFi [SM-t110], OS 4.2.2, Vivante GC1000 (OpenGL ES 2.0), Marvell PXA988 (we do not have this device)
Samsung Galaxy S III Mini VE with NFC [GT I8200N], OS 4.2.2, Vivante GC1000, Marvell
DUT(Not reproducible):
Samsung Galaxy Tab 3 Lite 7.0 [SM-T113], OS 4.4.4, GPU ARM Mali-400 MP2 , CPU Spreadtrum
Samsung Galaxy S IV LTE [GT-i9505], OS 4.2.2, GPU Adreno 320, CPU Qualcomm Snapdragon 600
HTC Desire 300 301e [HTC Z3 ], OS 4.1.2, GPU Adreno 203, CPU Qualcomm Snapdragon 200
Reproducible: 5.5.0b9, 5.5.3f1, 5.6.0f3, 2017.1.0b1
Note: According to Omar when build is made with Unity 2017.1 the app crashes at launch just right after the Unity splash screen plays.
It crashes only when there is a gap in curve that parameterizes particle size over lifetime. This project also has some gaps. TestSceneCrash>FX_PowerReady>Pentagons>Glow in Inspector Size Over Lifetime particle system curve has a gap. If I disable all particles which have a gap in size over lifetime, application
doesn't crash
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- "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
- Shortcut Manager shows empty conflict filter when resolving runtime conflicts involving different contexts
Add comment