Search Issue Tracker
Third Party Issue
Votes
0
Found in [Package]
1.3.2
Issue ID
ALB-11
Regression
No
[ChromeOS] Android Logcat doesn't detect any cores on AMD-9120C CPU Chromebook
How to reproduce:
1. Open a new Unity project
2. Build and Run on a Chromebook
3. Connect to Chromebook with Android Logcat
4. Search for the "SystemInfo" pattern in the search field
Expected result: Information provided about cores is greater than 0
Actual result: Information supplied about cores is equal to 0. Thus, Unity doesn't detect any cores on Chromebook
Reproducible with: 1.3.2 (2019.4.39f1, 2020.3.34f1, 2021.3.3f1, 2022.1.1f1, 2022.2.0a14)
Reproducible on: macOS 12.3 (Intel)
Reproducible with devices:
VLNQA00473 - AMD Stoney Ridge Chromebook (grunt), CPU: AMD A4-9120C Radeon R4, GPU: AMD STONEY (DRM 3.42.0, OS: 9
Not reproducible with devices:
VLNQA00421 - Google Pixelbook (Android 9): SystemInfo CPU = x86-64, Cores = 4, Memory = 7869mb
VLNQA00424 - Intel Comet Lake U Chromebook (hatch), CPU: -, GPU: virgl (Mesa DRI Intel(R) UHD Graphics (CML GT2)), OS: 11
VLNQA00425 - Google Pixelbook (Google Pixelbook), CPU: -, GPU: virgl (Mesa DRI Intel(R) HD Graphics 615 (KBL GT2)), OS: 11
VLNQA00432 - Chromebook x360 11 G1 EE(Android 9): SystemInfo CPU = x86-64, Cores = 2, Memory = 3827mb
VLNQA00455 - Intel Comet Lake U Chromebook (Android 11) : SystemInfo CPU = x86-64, Cores = 8, Memory = 6595mb
Note: The main issue is that not detecting any cores disables multi-threading rendering, and then no optimisation is available on such devices
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
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
Resolution Note:
Logcat only shows messages coming from the device.
This feels like Unity's Android Runtime issue, if so, please create a bug in appropriate area