Search Issue Tracker
Fixed in 5.4.0
Votes
2
Found in
5.3.1f1
Issue ID
756652
Regression
No
AssetBundle.LoadFromMemory uses more memory on device than AssetBundle.LoadFromFile
How to reproduce:
1. Open attached project (configured.zip)
2. Build to iOS and run
3. Open the Memory profiler screen in Xcode
4. Select the Load from File option on the device
- Note that the memory usage increases by about 10mb
5. Select the Go Back option
- Note that the memory usage goes down
- Repeating this process does not produce different results
6. Select the Load from Memory option
- Note that the memory usage increases by at least 30mb
7. Select the Go Back option
- Note that the memory usage barely goes down
8. Repeat from step 6
- This causes the memory usage to ramp up until it reaches about 71mb at its highest
- Reproduced in Version 5.4.0b4 (a7d7a3a2cef4), Version 5.3.1f1 (3b3e8231502f) on an iPhone 5 (iOS7), iPhone 6+ (iOS8)
- Blocked from testing Version 5.2.4f1 (98095704e6fe) due to missing features in that version
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- PlasticSCM NullReferenceException on entering the Play Mode when Unity Version Control tab is added to the layout
- Shortcut Helper Bar does not appear when enabling it and disabling it
- "Property (urp_ReflProbes_BoxMin) exceeds previous array size" warning spams console after switching platforms
- Have to change Input Mapping Path twice for change to take effect when Auto-Save is enabled
- No Duplicate option is available when right clicking States in the Animator Window even though it's available via Shortcut
Add comment