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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
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.