Search Issue Tracker
Active
Votes
0
Found in [Package]
1.22.2
2.2.2
Issue ID
ADDR-3792
Regression
No
[Android] A Significant spike in the performance occurs when loading a Texture2DArray with Addressables and Multithreaded rendering is enabled in certain Android devices
Reproduction steps:
1. Open the attached “ASQWE” project
2. Open the Profiler Window (Window > Analysis Profiler)
3. In the Profiler Window, select the connected device
4. Build and run the Player (File > Build And Run)
5. Observe the Profiler Window
Expected result: There are no significant spikes in the performance of the Player
Actual result: A significant spike in the performance occurs during the third texture load
Reproducible with: 1.22.2 (2022.3.50f1), 2.2.2 (6000.0.23f1)
Could not test with: 1.22.2 (2021.3.44f1 (“error CS0103: The name 'InstantiateAsync' does not exist in the current context” compilation error))
Reproducible environment: MacOS 14.6.1 (Intel), Windows 11 (user’s)
Not reproducible environment: No other environment tested
Reproducible on:
VLNQA00175, Samsung Galaxy Note9 (SM-N960F), Android 10, CPU: Exynos 9 (9810), GPU: Mali-G72
Not reproducible on:
VLNQA00146, Htc 10 (HTC 10), Android 8.0.0, CPU: Snapdragon 820 MSM8996, GPU: Adreno (TM) 530
VLNQA00057, Htc One M9+ (HTC_M9pw), Android 6.0, CPU: MediaTek Helio X10 MT6795T, GPU: PowerVR Rogue G6200
VLNQA00372, Samsung SM-G991U (SM-G991U), Android 12, CPU: Snapdragon 888, GPU: Adreno (TM) 660
VLNQA00382, Apple iPhone 7 (iPhone9,3), Android 13.1, CPU: Apple A10 Fusion, GPU: Apple A10 Fusion
MacOS Buildtime, Runtime
Could not test on:
VLNQA00519, Google Pixel 4 (Pixel 4), Android 12, CPU: Snapdragon 855 SM8150, GPU: Adreno (TM) 640
(The application crashes on startup)
Workaround: Disable the Multithreaded Rendering
Note: Only occurs the first time
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Add comment