Search Issue Tracker
Duplicate
Votes
1
Found in
2019.4.20f1
Issue ID
1319431
Regression
Yes
[iOS] SystemInfo.systemMemorySize returns negative values
Steps to reproduce:
1. Open the project attached by the user
2. Build and deploy the project to a device
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.0a7
Reproducible on:
- 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
- [iOS] Crash on ScriptingGCHandle::Acquire when calling RequestUserAuthorization without using yield for pending authorization
- Particle is not visible in RenderTexture when Renderer's material is set to Default-Particle and Camera's BG Alpha is set 0
- OnTriggerExit is not called when GameObject leaves Trigger through reparenting
- [Physics] Character Joint jumps around when following Kinetic Rigidbody
- [macOS] There is no way to tell if you are running under Rosetta
shochet
Mar 29, 2021 19:41
Just found this same bug (2019.4.22) looks like it is fixed in the 2019.4.23 release notes:
iOS: Fixed a regression that meant devices with memory over 2GB reported negative amounts of memory. (1319420)
user1dedalord
Mar 22, 2021 21:30
Why is this marked as duplicated with no link to the "original" report? I cannot find it anywhere and every other similar issue is marked as fixed when I'm still experiencing it on version 2019.4.20f1
jtate5
Mar 08, 2021 16:53
This is a major issue. Will it be resolved soon?