Memory leak in FRealtimeMeshSectionGroupSimple on async rebuild of collisions

[OriginalAxle]

Description:

There appears to be a memory leak in the async update of collision meshes, specifically in URealtimeMeshSimple. Trace file captures (screenshots attached to this report) are available upon request (Associated bug is in the bug report feed and help channels)

Proconditions:

Given a cube mesh where each side is subdivided into four quadrants.
and Collision + Mesh builder:

RealtimeMesh = RealtimeMeshComponent->InitializeRealtimeMesh();

Mesh builder
meshBuilder = TSharedPtr<TRealtimeMeshBuilderLocal<uint32, FPackedNormal, FVector2DHalf, 1>>(new TRealtimeMeshBuilderLocal<uint32, FPackedNormal, FVector2DHalf, 1>(streamedMeshData));

meshBuilder->EnableTangents();
meshBuilder->EnableTexCoords();
meshBuilder->EnableColors();
meshBuilder->EnablePolyGroups();

Config definition
FRealtimeMeshCollisionConfiguration CollisionConfig;
CollisionConfig.bUseAsyncCook = false; <------- IF SET TO TRUE, PROBLEM HAPPENS
CollisionConfig.bUseComplexAsSimpleCollision = true;
CollisionConfig.bShouldFastCookMeshes = false;
CollisionConfig.bDeformableMesh = false;
CollisionConfig.bFlipNormals = false;

---

Steps to reproduce:

1. Instantiate the mesh

groupKey = FRealtimeMeshSectionGroupKey::Create(0, FName("chunkMesh"));
RealtimeMesh->CreateSectionGroup(groupKey, streamedMeshData);
RealtimeMesh->SetupMaterialSlot(0, "PrimaryMaterial", voxelManager->voxelMaterial);
PolyGroup0Key = FRealtimeMeshSectionKey::CreateForPolyGroup(groupKey, 0);
RealtimeMesh->UpdateSectionConfig(PolyGroup0Key, RealtimeMesh->GetSectionConfig(PolyGroup0Key), true);

2. Modify the mesh (remove a sub division)
3. Check memory

Important notes:

1. Mesh collision memory scales with mesh complexity, causing simple test cases to not adequately report the memory leak
2. I have attached in the original post the images of unreal insights trace and some code showing the problem happening at runtime
3. Problem does not occur when the RealtimeMeshComponent is reinitialized at runtime implying the problem does not occur in component destruction

UPDATE 1:
After some additional tracking there appears to be another reporting of the issue here

UPDATE 2:
Was unable to get the collision mesh to properly generate when async generation flag was false in collision config

Associated trace screenshot