Search Issue Tracker

Fixed in 2022.1.X

Fixed in 2020.3.X, 2021.1.X, 2021.2.X



Found in







Issue ID




Memory leak occurs in Player as SharedGeometryBuffers mismatches memory labels for NEW and DELETE



How to reproduce:
1. Open the attached project ""
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

- The issue is reproducible on Windows Standalone builds
- The issue occurs because m_GeometryBuffers in Mesh is allocated as kMemSerialization, and deallocated as kMemGeometry

  1. Resolution Note (fix version 2022.1):

    Fixed in 2022.1.0a10

  2. Resolution Note (fix version 2021.2):

    Fixed in: 2021.2.1f1

  3. Resolution Note (fix version 2021.1):

    Fixed in: 2021.1.26f1

  4. Resolution Note (fix version 2020.3):

    Fixed in: 2020.3.24f1

Comments (1)

  1. SLGSimon

    Dec 08, 2021 13:13

    Is this an actual memory leak, or just a reporting issue?

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.