Search Issue Tracker
Won't Fix
Votes
0
Found in
2018.3.13f1
Issue ID
1162264
Regression
No
Application crashes while warming up shader variant collection on Amazon Kindle when shader has uniform float array size 256
To reproduce:
1. Open attached project 'AdrenioAndroidVulkanGraphicsTest.zip"
2. Build and run on Android device
3. Observe the crash (if it doesn't crash automatically after 5-10 seconds, interact with the screen, for example try expanding status bar)
Result: built application crashes (appNotResponding)
Reproduced in: 2017.4.29f1, 2018.4.2f1, 2019.1.6f1, 2019.2.0b6, 2019.3.0a6
Reproduced on device:
VLNQA00113, Amazon Kindle Fire HDX 7" (2013) (KFTHWI), Android 4.4.3, CPU: Snapdragon 800 MSM8974, GPU: Adreno (TM) 330
Not reproducible on devices:
VLNQA00031, Lge Nexus 5 (Nexus 5), Android 6.0.1, CPU: Snapdragon 800 MSM8974, GPU: Adreno (TM) 330
VLNQA00040, Htc ONE S (HTC One S), Android 4.1.1, CPU: Snapdragon S4 MSM8290, GPU: Adreno (TM) 225
VLNQA00267, Samsung Galaxy S10+ (SM-G975F), Android 9, CPU: Exynos 9 9820, GPU: Mali-G76
VLNQA00274, Oculus (Quest), Android 7.1.1, CPU: Snapdragon 835 MSM8998, GPU: Adreno (TM) 540
VLNQA00076, Amazon Fire HD 8 (2015) (KFMEWI), Android 5.1.1, CPU: MediaTek MT8135, GPU: PowerVR Rogue G6200
VLNQA00074, Amazon Fire (2015) (KFFOWI), Android 5.1.1, CPU: MediaTek MT8127, GPU: Mali-450 MP
VLNQA00035, Motorola DROID MAXX 2 (XT1021), Android 4.4.4, CPU: Snapdragon S4 Pro, GPU: Adreno (TM) 305
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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- Crash with “Fatal Error! The file ‘MemoryStream’ is corrupted!” when adding a large number in Font Character Rects Size field
Resolution Note (2019.3.X):
Won't fix: drivers issue, limited to specific device.