Search Issue Tracker

Won't Fix



Found in








Issue ID




[FrameDebugger] "Draw Mesh (instanced)" not shown in Frame Debbuger when debugging a device with Mali GPU



Reproduction steps:
1. Open the attached user's Unity project ""
2. Go to File > Build Settings and select Development Build
3. Build and Run the application on a device
4. Go to Windows > Analysis and open the Frame Debugger window
5. Enable the Frame Debugger on a device
6. Expand everything in the menu on the left side
7. Observe "Draw Mesh" in the list

Expected result: "Draw Mesh (instanced)" is shown in the Frame Debugger
Actual result: "Draw Mesh" is shown in the Frame Debugger

Reproducible with: 2019.4.37f1, 2020.3.32f1, 2021.2.19f1, 2022.1.0b15, 2022.2.0a9

Reproduces with these devices:
VLNQA00458 - Google Pixel 6 (Pixel 6), CPU: Google Tensor (Whitechapel), GPU: Mali-G78, OS: 12
VLNQA00006 - Samsung Galaxy S7 (SM-G930F), OS: 8.0.0, CPU: Exynos 8 Octa (8890), GPU: Mali-T880
VLNQA00121 - Samsung Galaxy S9 (SM-G960F), OS: 9.0.0, CPU: Exynos 9 Series 9810, GPU: Mali-G72

Not reproducible with these devices:
VLNQA00404 - Galaxy Z Flip3 5G (SM-F711B), OS: 11, CPU: Snapdragon 888, GPU: Adreno 660
VLNQA00277 - Asus ROG Phone (ASUS_Z01QD), OS: 9.0.0, CPU: Snapdragon 845 SDM845, GPU: Adreno 630
VLNQA00022 - Xiaomi Redmi Note 3 (Redmi Note 3), OS: 6.0.1, CPU: Snapdragon 650 MSM8956, GPU: Adreno 510
VLNQA00147 - Razer Phone (Cheryl), OS: 8.1.0, CPU: Snapdragon 835 MSM8998, GPU: Adreno 540
VLNQA00219 - Samsung Galaxy Note9 USA (SM-N960U), OS: 8.1.0, CPU: Snapdragon 845 SDM845, GPU: Adreno 630
(User's info) Xperia 5 Ⅱ
(User's info) Google Pixel 4 XL
(User's info) LG V60 ThinQ 5G
(User's info) OPPO Find X2 Pro
(User's info) Galaxy Note10+
(User's info) Galaxy Note20 Ultra 5G
(User's info) arrows NX9
(User's info) Axon 10 Pro 5G
(User's info) AQUOS R6

  1. Resolution Note:

    Thank you for your bug report.

    After reviewing the issue and the impact it has on our users our team has decided that this case will be resolved as "Won't Fix".This does not mean that the issue isn’t a legitimate bug, but instead that we are not able to prioritize the fix, at this time.

    The case will now be closed, and will not be reopened unless new information arises that would change the issue’s impact. Please let us know if you have additional information relating to the severity of this bug.

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.