Search Issue Tracker
Won't Fix
Votes
0
Found in
2021.2.0b4
2022.1
Issue ID
1352486
Regression
No
[iOS] Memory Settings of iOS Player has no effect.
Unity 2021.2 Editor introduced allocator thread block settings (Project Settings > Memory Settings). These settings are used when setting up dynamic heap allocator. On iOS platform dynamic heap allocator is supported only when running on simulator, not on a device. Therefore these memory settings have no effect on iOS player running on device. These Project Settings are misleading.
It should be investigated why dynamic heap allocator is disabled on iOS when running on device (there might be a sound reason for that). If dynamic heap allocator should stay disabled, memory settings for iOS target should be disabled as well, or have an indication that changing memory settings will not have effect when project is run on iOS devices.
Reproducible with: 2021.2.0b4, 2021.2.0b5, 2022.1.0a3
Not reproducible with: 2018.4, 2019.4, 2020.3, 2021.1, 2021.2.0b3
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
- ADB PRovider is really slow
- "System.Net.CookieContainer" throws an "ArgumentException" error when using a non-UTF-8 machine locale and hostname
- Crash on ModelImporter::ImportSkinnedMesh when disabling "Strip Bones" on a specific FBX model
- WebGL Development builds ignore the "Compression Format" setting when using "Gzip" compression
- [tvOS] Project crashes on startup on Apple TV simulator (both X86_64 and ARM64 architectures)
Resolution Note (2022.1.X):
Dynamic heap allocator is going to be enabled on iOS in near future and the settings will have an effect.