Search Issue Tracker
Active
Votes
0
Found in
6000.0.29f1
6000.1.0a6
Issue ID
UUM-88991
Regression
Yes
Texture2D memory allocation size is significantly increased when running on iOS device
Reproduction steps:
1. Open the attached “BugRepro” project
2. In the Build Profile window, enable Development Build option
3. Build the project and run it on an iOS device
4. In the Memory Profiler (Window > Analysis > Memory Profiler), attach it to the iOS device
5. Capture and inspect a memory snapshot
6. In the Unity Objects tab, observe the “Texture2D” Allocated size
Expected result: The allocated size is low, around 25MB
Actual result: The allocated size is 188 MB or more
Reproducible with: 6000.0.29f1, 6000.1.0a6
Not reproducible with: 2022.3.53f1
Couldn't test with: 2021.3.46f1 (Undefined symbol errors when building in Xcode)
Testing environment: macOS Sequoia 15.1.1 (M1 Max)
Reproducible with these devices:
VLNQA00624, iPhone 16 Pro, iOS 18.0.1, CPU: Apple A18 Pro
VLNQA00394, iPhone 13 mini, iOS 18.1, CPU: Apple A15 Bionic
VLNQA00359, iPhone 12 Pro, iOS 17.6.1, CPU: Apple A14 Bionic
Couldn’t test with these devices:
VLNQA00363, Samsung Galaxy Z Fold 2 5G, Android 12, CPU: Snapdragon 865 SM8250, GPU: Adreno 650 (errors when launching the project)
Note: If you build the project on an unaffected version and then port to and build the project on an affected version, the issue is not reproducible. To solve this, you have to delete the Library folder in the project directory before building
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Linux] "Trying to load color backbuffer into a complex RenderPass setup" error is thrown after entering Play mode in AR Mobile template project
- [Android] Neither of the callbacks are called when several videos with VideoPlayer are spawned on the target on the Google Pixel devices
- Texture2D memory allocation size is significantly increased when running on iOS device
- No data received in Profiler when connecting to WebGL Player without "Autoconnect Profiler" option enabled
- Screen Space Ambient Occlusion is ignored when toggling "Post Processing" visibility in the Scene window overlay
Add comment