Search Issue Tracker
Fixed
Fixed in 2.3.3
Votes
1
Found in [Package]
2.2.2
2.3.0
Issue ID
ABC-318
Regression
No
Memory is leaking when using Alembic package
To reproduce:
1. Open the project “Alembic Memory leak”
2. Open the Memory Profiler window (Window → Analysis → Memory Profiler)
3. Open and run the "Empty" scene
4. Take a snapshot in the Memory Profiler
5. Press 1 on the keyboard to change to a scene containing Alembic animations
6. Press 2 on the keyboard to go back to the empty scene
7. Take a snapshot in the Memory Profiler
8. Notice System.Int32\[] block size (select Snapshot → Tree Map)
Expected result: System.Int32\[] block size at the 7th and 12th steps is the same
Actual result: System.Int32\[] block size at the 12th step is almost twice as big as at the 7th step
Reproducible with: 2.2.2 (2020.3.36f1, 2021.3.6f1), 2.3.0 (2022.1.9f1, 2022.2.0a18)
Could not test with: 2023.1.0a2 (Could not find Tree Map)
Reproduced on: macOS Monterey 12.4 (Intel)
Note: After repeating 5, 6, 7 steps each time System.Int32\[] size increases
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Shader Graph Asset icon is not shown on creation unless you confirm the name
- APV Sky occlusion doesn't consider the terrain
- [iOS] "EXC_BAD_ACCESS" Player crash when Script Debugging is enabled
- Cursor skips input fields when tabbing between two sets of input fields
- "Shader error redefinition of 'Varyings'" error appears when selecting the shader
Add comment