Search Issue Tracker
Not Reproducible
Fixed in 2019.4.X
Votes
0
Found in
2019.4.20f1
Issue ID
1319420
Regression
Yes
[iOS] If memory of device is 2GB over, SystemInfo.systemMemorySize is returned wrong value on IOS
Step to reproduce:
1. Open the attached project ("1319420.zip")
2. Build and deploy the project to a device with more than 2GB of memory
Expected result: SystemInfo.systemMemorySize returns a correct amount of memory that the device has
Actual result: SystemInfo.systemMemorySize returns a negative amount of memory
Reproducible with: 2019.4.20f1, 2019.4.22f1
Not reproducible with: 2018.4.32f1, 2019.4.19f1, 2020.3.0f1, 2021.1.0b11, 2021.2.0a19
Reproducible on:
iPhone 7 (2GB)
iPhone 11 Pro (4GB)
iPhone XR (13.4.1)
iPhone 8 Plus (12.0)
Not reproducible on:
- iPhone 12 Pro (iOS 14.2.1)
- iPhone 6S (iOS 13.3.1)
- iPad 9.7" 6th gen (14.4)
- iPad Air 2 (11.0.3)
- VLNQA00013, Samsung Galaxy S6 Edge Plus (SM-G928F), Android 7.0, CPU: Exynos 7 Octa 7420, GPU: Mali-T760
- VLNQA00122, Samsung Galaxy S9 (SM-G960F), Android 10, CPU: NOT FOUND, GPU: Mali-G72
- VLNQA00331, Huawei P20 lite (ANE-LX1), Android 9, CPU: HiSilicon Kirin 659, GPU: Mali-T830
- VLNQA00285, Samsung Galaxy J4 Core (SM-J410F), Android 8.1.0, CPU: Snapdragon 425 MSM8917, GPU: Adreno (TM) 308
- VLNQA00321, Xiaomi MI 9 (MI 9), Android 10, CPU: Snapdragon 855 SM8150, GPU: Adreno (TM) 640
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
- 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
Resolution Note (2021.2.X):
Issue was never introduced in trunk, thus not reproducible. Fixed in 2019.4.23f1 by a backport