Reproduction steps:
1. Open the “ASDQWE” project
2. Build and run the Player (File > Build And Run)
3. Observe the text’s value in the middle of the Player

Expected result: The value matches the device’s nominal processor’s frequency
Actual result: The value does not match the device’s nominal processor’s frequency

Reproducible with: 2021.3.44f1, 2022.3.48f1, 6000.0.21f1

Reproducible environment: MacOS 14.6.1 (Intel), Windows 10 (user’s)
Not reproducible on: No other environment tested

Reproducible on:
VLNQA00519, Google Pixel 4 (Pixel 4), Android 12, CPU: Snapdragon 855 SM8150, GPU: Adreno (TM) 640
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
MacOS Buildtime, Runtime
Redmi 9T, CPU: Qualcomm Snapdragon 662, GPU: Adreno 610 (user’s)

Not reproducible on:
VLNQA00175, Samsung Galaxy Note9 (SM-N960F), Android 10, CPU: Exynos 9 (9810), GPU: Mali-G72
VLNQA00146, Htc 10 (HTC 10), Android 8.0.0, CPU: Snapdragon 820 MSM8996, GPU: Adreno (TM) 530

Could not test on:
VLNQA00382, Apple iPhone 7 (iPhone9,3), Android 13.1, CPU: Apple A10 Fusion, GPU: Apple A10 Fusion
(“0” value is displayed)

Notes:
- The Samsung SM-G991U and Google Pixel 4 displayed roughly twice the expected value
- The Htc One M9+ displayed slightly higher (2158) than what is expected (~2000)
- The issue can be reproduced on a blank project