Search Issue Tracker
Third Party Issue
Votes
0
Found in
2019.4
2020.3
2020.3.4f1
2021.1
2021.2
2022.1
Issue ID
1329920
Regression
No
[Android] "mali.instrumentation.graph.work: key already added" is spammed in the Build logs
How to reproduce:
1. Create a new project
2. Open the Build Settings (File->Build Settings...)
3. Switch Platform to Android
4. Check the Development Build
5. Open any Scene to Scenes In Build
6. Build And Run
7. Log the development build using "adb logcat"
8. Inspect the logs
Expected results: Multiple "mali.instrumentation.graph.work: key already added" messages in the logs
Actual results: No "mali.instrumentation.graph.work: key already added" messages in the logs
Reproducible with: 2019.4.29f1, 2020.3.16f1, 2021.1.17f1, 2021.2.0b7, 2022.1.0a5
Reproducible on:
N/A, Samsung Galaxy S10 (SM-G973F), Android 11, CPU: NOT FOUND, GPU: Mali-G76
Not reproducible on:
VLNQA00286, Meizu Pro 5 (PRO 5), Android 7.0, CPU: Exynos 7 Octa 7420, GPU: Mali-T760
VLNQA00313, Huawei Y6 Ⅱ Compact (HUAWEI LYO-L01), Android 5.1, CPU: MediaTek MT6735, GPU: Mali-T720
VLNQA00294, Oppo OPPO Reno Z (PCDM10), Android 11, CPU: NOT FOUND, GPU: PowerVR Rogue GM9446
VLNQA00335, Samsung Galaxy S20+ 5G (SM-G986B), Android 10, CPU: Exynos 990, GPU: Mali-G77
VLNQA00362, Samsung Galaxy Z Fold2 5G (SM-F916U1), Android 11, CPU: Snapdragon 865 SM8250, GPU: Adreno (TM) 650
N/A, Samsung Galaxy S9 (SM-G960F), Android 8.0.0, CPU: Exynos 9 Series 9810, GPU: Mali-G72
VLNQA00318, Oneplus 7Pro (GM1913), Android 10, CPU: Snapdragon 855 SM8150, GPU: Adreno (TM) 640
VLNQA00231, Huawei HUAWEI Mate 20 Pro (LYA-L29), Android 9, CPU: HiSilicon Kirin 980, GPU: Mali-G76
VLNQA00024, Xiaomi Mi 5 (MI 5), Android 7.0, CPU: Snapdragon 820 MSM8996, GPU: Adreno (TM) 530
VLNQA00264, Samsung Galaxy S10+ (SM-G975F), Android 10, CPU: NOT FOUND, GPU: Mali-G76
VLNQA00279, Samsung Galaxy S10+ (SM-G975U), Android 9, CPU: Snapdragon 855 SM8150, GPU: Adreno (TM) 640
Note:
- Reproducible with both Mono and IL2CPP builds
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
- Crash when trying to force Shader to interpret 1/30 as a floating point operation
- Terrain is flickering when adjusting "Compatibility Mode" and "Use Rendering Layers" Settings
- Isometric tiles are flickering and overlapping each other when entering Play Mode with Tilemap Renderer mode set to "Chunk"
- Crash on ParticleSystemParticles::array_reserve when particle system starts
- Docking Text Property Preview Window next to UI Builder breaks the window and causes NullReferenceException
yhunroh
Aug 10, 2021 09:33
I had this issue on 2020.1.14, and after I added OpenGLES2 and made Vulkan low-priority, the message stopped.
I guess this happens when Android build uses Vulkan?