Search Issue Tracker
Won't Fix
Votes
0
Found in
2020.3.48f1
Issue ID
UUM-43151
Regression
No
AudioClip memory usage on device is always 1MB
How to reproduce:
1. Download and open the attached project
2. Build and deploy to iOS
3. Capture using Memory Profiler
4. Open capture and navigate to Tree Map
5. Filter by AudioClip (right click Type column, click 'Match', type 'AudioClip in filter)
Expected outcome: All audioclips have size in relation to their real size
Actual outcome: One audioclip (in this case, new level_render 002) will have a size of 1.0MB
Reproducible with: 2020.3.48f1, 2021.3.28f1, 2022.3.5f1, 2023.1.5f1, 2023.2.0b1
Reproduced with: iPhone 12 Pro (iOS 14.2.1), iPhone 13 (iOS 15.0.1)
Note: there will always be one audio file set to 1MB. If for instance new level_render 002 is deleted, one of the other audio files will suddenly become 1MB.
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
- VFX Graph Memory leak when calling the ClearPropertyBinders and AddRemoveVFXProperty
- Entering "Configure Avatar" inside the Inspector locks it
- [Render Graph Viewer] Resource list icons cropped and in inconsistent positions
- Scene View with Debug Draw Mode enabled is gray when GPU Resident Drawer is enabled
- The UI is not visible when resizing out of focus built Player window with Application.runInBackground set to false
Resolution Note:
Thank you for your bug report.
After reviewing the issue and the impact it has on our users our team has decided that this case will be resolved as "Won't Fix".This does not mean that the issue isn’t a legitimate bug, but instead that we are not able to prioritize the fix, at this time.
The case will now be closed, and will not be reopened unless new information arises that would change the issue’s impact. Please let us know if you have additional information relating to the severity of this bug.
Here is a little bit of additional information we learned about this issue:
- It's related to Vorbis files that are compressed in memory. If you decompress the files at startup or use another compression format, the mystery 1MB goes away in the profiler.
- When it comes to the problematic audio asset, the size of the audio asset is still accounted for in the profiler but it has 1MB added to its size.
- We think this is in some way related to Vorbis decompression state that gets allocated when we have an active Vorbis decoder, and that memory is getting added in error to the asset's size in the memory profiler.