Search Issue Tracker
Won't Fix
Votes
1
Found in
5.4.2p2
Issue ID
849083
Regression
No
[iOS] Increased memory usage (about two times more) until library is rebuilt
Reproduction steps:
1. Download the "Archive" attached project.
2. Build and run it for iOS.
3. Click a sign with a play symbol in the application.
4. Open a Debug navigator and select Memory in the Xcode.
- Memory usage should be about 350 - 400("Actual" screenshot).
5. Delete library folder and repeat steps 2 - 4.
- Memory usage should be about 200("Expected" screenshot).
Reproduced with:
- 5.4.0p4
- 5.4.2p2
- 5.4.3f1
- iPad Air 2 9.3.2
Notes:
- We are not sure how to corrupt a library folder. Maybe library folder comparison would help.
- Our guess is that multiple unused sprite atlas versions are included.
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
- Objects with Universal Render Pipeline/Particles/Lit shader are always lit up when changing their Rendering Layer Mask
- PolySpatial “Trying to set shader on a Material Variant.” error is printed in the console when entering Play Mode
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
- Addressables content build fails but the Player build is successful when building a development build
Resolution Note:
The issue seems to be very corner-case. We have never received similar bug reports since then. Also, the Unity version reported is long gone.