Search Issue Tracker
Fixed in 2022.1.X
Fixed in 2020.3.X, 2021.1.X, 2021.2.X
Votes
0
Found in
2019.4
2020.3
2021.1
2021.2
2021.2.0b6
2022.1
Issue ID
1362505
Regression
No
Memory leak occurs in Player as SharedGeometryBuffers mismatches memory labels for NEW and DELETE
How to reproduce:
1. Open the attached project "URP_template_2021.zip"
2. When using 2021.2.0b1 and above, go to Edit > Project Settings > Memory Settings > Players > Main Allocators > Shared Bucket Allocator, and set Bucket Allocator Block Count to 1 MB
3. In File > Build Settings, make sure that Scenes/Startup, Scenes/SampleScene, and Scenes/Empty are added to Scenes In Build, and Development Build and Autoconnect Profiler are enabled
4. Build and Run
5. In Editor, open Window > Analysis > Profiler, and make sure that the Memory module is chosen and view is set to Detailed
6. In the Profiler tab, click the Take Sample button
7. In the snapshot, check the value for Other > Objects
8. Repeat steps 6-7
Expected results: the value stays the same
Actual results: the value increases
Reproducible with: 2019.4.29f1, 2020.3.18f1, 2021.1.20f1, 2021.2.0b11, 2022.1.0a7
Not reproducible with: 2019.4.30f1
Notes:
- The issue is reproducible on Windows Standalone builds
- The issue occurs because m_GeometryBuffers in Mesh is allocated as kMemSerialization, and deallocated as kMemGeometry
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
- [Dragon Crashers] Build fails in U6
- [Dragon Crashers] 4 Shader error messages on import
- [Dragon Crashers] Readme text is white on light grey
- Cursor stays in front of the first character when entering text in the TextMeshPro field
- Searching in Hierarchy causes unwanted component calls
Resolution Note (fix version 2022.1):
Fixed in 2022.1.0a10
Resolution Note (fix version 2021.2):
Fixed in: 2021.2.1f1
Resolution Note (fix version 2021.1):
Fixed in: 2021.1.26f1
Resolution Note (fix version 2020.3):
Fixed in: 2020.3.24f1