Procedural Mesh Component Memory leak when destroyed from an Array

When destroying an Actor with a Procedural Mesh Component; that is stored in an Array Variable, the memory for that Actor's Procedural Mesh Component is not cleared, leading to a Memory Leak. However, If you make the actor into a Single Variable and destroy it, that Procedural Mesh's memory is properly cleared by Unreal's Garbage Collection.

NOTE: See attachment  "MemoryLeak_Example.zip"  for simplified project source replication. 

Open Unreal Engine 4.20-> Create Third Person Blueprint Template.

Creating Procedural Mesh Actor

1. Inside of Content Folder-> Create a new Blueprint Actor class. "TestActor"
2. Inside of Blueprint Actor-> Add Component-> Procedural Mesh
3. Inside of Blueprint Actor->Construction Script-> Create new local variable
4. Name local Variable "Vertices" and choose Vector Array for Variable Type->Compile.
5. Populate the Array with 8 elements, set the vector coordinates as shown in attached file: ProceduralMeshActor.png.
6. Create a local Variable "Triangles", and choose Integer Array for Variable Type->Compile.
7. Populate the Array with 36 elements, set default values as shown in attached file: ProceduralMeshActor.png

Creating a new Blueprint Player Controller

1. Create a new Blueprint Player Controller
2. Inside of Player Controller Blueprint-> Create a new variable called "Chunk Test Array" of type "TestActor", and make it an Array->Compile.
3. Inside of Player Controller Blueprint->Create a new variable of type integer, named "MeshIDs"->Compile.
4. Drag off of the event tick node of the Player Controller event graph, and implement the following. (see attached file: PlayerControllerEventGraph.PNG) 

Playing in Editor

1. Create a new Blueprint Game Mode.
2. Change Player Controller class to PlayerController Blueprint.
3. Change Default pawn class to ThirdPersonCharacter.
4. Go to Project settings->Maps&Modes-> Choose Gamemode_Bp for Default Game mode.
5. Open up Windows Task Manager to monitor memory usage.
6. Play in Editor
      

Expected: The Memory used by the Procedural Mesh Component is cleared when the Actor is destroyed.

Result: The memory usage of Unreal Engine will keeping going up while you play until your computer runs out of memory and the game/editor crashes. The actor is successfully destroyed, yet the memory taken by the mesh geometry is still remaining.

Fix UE-51650

i have this problem UE4CC-Windows-58DC12AF4B97F057BD108FBFF569B2E9_0000

Delay nodes occasionally don't fire the "Completed" output in a nativized build

Undefined sysmbol: typeinfo for AActor when cross-compile linux dedicated server on windows

I am not able to find world outliner how to enable it?

An error occurred while trying to generate project files !?

How can i modify the param name in EQS node

Bonjour j'ai un petit problème c'est que je ne vois plus l'onglet "scability" pour changer les graphismes de uefn et j'ai pas trouvé l'option pour le faire revenir ?

Error UE5 5.0.3

Installer 4.10 failed with error code R-1603