Search Issue Tracker
Active
Votes
0
Found in
2021.3.46f1
2022.3.53f1
6000.0.31f1
6000.1.0a8
Issue ID
UUM-90475
Regression
No
[Android] Gfx.WaitForGfxCommandsFromMainThread high performance usage and inconsistency when built Player scene has Canvas GameObject on a specific Project
How to reproduce:
1. Open the attached “IN-83694.zip” Project
2. Open the Profiler Window (Window → Analysis → Profiler)
3. Change the “Module Details panel” to Timeline
4. Connect a mobile device and Build and Run on it
5. In the Profiler target the connected device
6. Wait for the Profiler to receive CPU usage data
7. Select any point in the “Frame Chart”
8. Observe the “Render Thread” sections “Gfx.WaitForGfxCommandsFromMainThread” performance usage
9. Back out to the Home section in the device (Send the app to the Foreground)
10. Re-open the Player in the device and re-target the device in the Profiler
11. Observe the “Render Thread” sections “Gfx.WaitForGfxCommandsFromMainThread” performance usage
Expected result: Consistent performance and or low usage
Actual result: Significant performance usage (~24.5ms) and inconsistent
Reproducible with: 2021.3.46f1, 2022.3.53f1, 6000.0.31f1, 6000.1.0a8
Testing environment: Windows 11
Reproducible on:
VLNQA00499, Google Pixel 7 (Pixel 7), Android 15, CPU: Google Tensor G2, GPU: Mali-G710
VLNQA00498, Google Pixel 7 (Pixel 7), Android 13, CPU: Google Tensor G2, GPU: Mali-G710
VLNQA00517 - OnePlus 10 Pro 5G (NE2213), CPU: Snapdragon 8 Gen 1 (SM8450), GPU: Adreno 730, OS: 12
VLNQA00411 - Galaxy Z Fold3 5G (SM-F926B), CPU: Snapdragon 888, GPU: Adreno 660, OS: 11
VLNQA00374 - Galaxy S21 Plus 5G (SM-G996U), CPU: Snapdragon 888, GPU: Adreno 660, OS: 11
VLNQA00218 - Samsung Galaxy Note 9 USA (SM-N960U), CPU: Snapdragon 845 SDM845, GPU: Adreno 630, OS: 8.1.0
VLNQA00122 - Samsung Galaxy S9 (SM-G960F), CPU: Exynos 9 Series 9810, GPU: Mali-G72, OS: 10.0.0
Not reproducible on:
VLNQA00557 - Google Pixel XL (Pixel XL), CPU: Snapdragon 821 MSM8996 Pro, GPU: Adreno 530, OS: 10
Notes:
- Note that user reported the performance degradation with Gfx.WaitForPresentOnGfxThread, however this was not observed and the issue was not only reproducible on Google Pixel 7 phones
- Using OpenGLES3 Graphics API appears to lower the Gfx.WaitForGfxCommandsFromMainThread usage but raises the RenderLoop usage from ~1.00-3.00ms to ~20.00ms
- Not reproducible on Standalone and Editor Play Mode
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- UI Source Image property gets set to 'None' when using a specific Sprite and Play mode is entered
- Rendering locks up when not looking at a transparent material on Meta Quest 2
- Volumetrics break when using a Custom Pass to create a Thickness Buffer for Alpha Clipping
- All tests are run instead of only the failed ones when the "Rerun Failed" button is pressed
- GameObject is not masked when the "Render PostProcessing Effects" pass executes with a resolved non-MSAA Color target and MSAA DepthStencil target
Add comment