Search Issue Tracker
Fixed in 2022.2.X
Fixed in 2020.3.X, 2021.3.X, 2022.1.X
Votes
0
Found in
2019.4
2020.3
2020.3.15f2
2021.2
2021.3
2022.1
2022.2
Issue ID
1410384
Regression
No
Allocated Memory Block with No Root Area cannot be tracked when loading Asset Bundles
How to reproduce:
1. Open the attached project (64MB-Test.zip)
2. Go to Window -> Analysis -> Memory Profiler
3. Select Capture -> Take Snapshot and select the captured snapshot
4. Select the Objects and Allocations tab, change "Select Table View:" to All Native Allocations, sort the table by descending size, and observe the memory blocks
5. Go to Window -> AssetBundle Browser
6. In the AssetBundles window, select the Inspect tab, then Add File
7. Add the file Assets/StreamingAssets/common_ui.assetbundle
8. Repeat steps 2, 3, 4
Expected result: Single Large Allocation Memory Block with No Root Area is not found
Actual result: Single Large Allocation Memory Block with No Root Area is found
Reproducible with: 2019.4.37f1, 2020.3.33f1, 2021.2.19f1, 2021.3.0f1, 2022.1.0b15, 2022.2.0a9
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
- Editor Perforce login fails when Perforce shows a license expiry warning
- Assertion failed error in HDRP builds when enabling STP via script
- FBX Resamples Curves incorrectly when importing FBX files
- ProBuilder GameObject Faces disappear when increasing the Sides Count value
- FileUtil.CopyFileOrDirectory throws IOException when destination parent folder does not exist
Resolution Note (fix version 2022.2):
Fixed in 2022.2.0a14
Resolution Note (fix version 2022.1):
Fixed in 2022.1.8f1
Resolution Note (fix version 2021.3):
Fixed in 2021.3.6f1
Resolution Note (fix version 2020.3):
Fixed in 2020.3.36f1