Copyright © 2026 Unity Technologies
Thank you for reporting a bug to Unity. After reviewing the behavior, we've confirmed it aligns with the current design and intended use of the feature. We understand this may differ from your expectations or workflow. We will close this case as 'As Designed.' If you have feedback on how the feature could better meet your needs, please let us know - we value your input and consider it in future improvements.
Steps to reproduce:
1. Open the attached project “IN-130195”
2. In the Project window, open Scene → “SampleScene”
3. Go to File → Build Profiles, select iOS
4. Build and Run
5. Install the Player using Xcode to your device
6. In the Player, wait for it to load and press the “Load1” button
Actual result: The app after loading shows “Graphics Max” and “Total Max” memory usage shows about 200~300mb higher than the current usage (about double)
Expected result: The maximum memory usage isn’t as big as double the current usage of memory
Reproducible with: 6000.0.45f1, 6000.0.65f1, 6000.3.6f1, 6000.4.0b5, 6000.5.0a5
Could not test with: 6000.0.44f1 (Xcode doesn’t compile the project)
Built on: macOS 26.1 (M1 Pro)
Reproducible with these devices:
VLNQA00328 - iPhone SE (2nd gen) (MX9U2ET/A), CPU: Apple A13 Bionic, GPU: PowerVR GT7600, OS: 14.3
VLNQA00625 - iPhone 16 Pro Max (MYWX3QN/A), CPU: Apple A18 Pro, OS: 18.0.1
Not reproducible with these devices:
VLNQA00382 - iPhone 7 (MN8Y2ET/A), CPU: t8010, GPU: PowerVR GT7600 Plus, OS: 15.8.3
VLNQA00189 - iPhone SE (1st gen) (MLLP2LP/A), CPU: Apple A9 (Samsung), GPU: PowerVR GT7600, OS: 15.8.3
Issues you vote on will appear here