From 1b52815584fbce5d47d9364e06873b282a8d27dd Mon Sep 17 00:00:00 2001
From: Steve Streeting <steve@stevestreeting.com>
Date: Thu, 16 Feb 2023 17:52:05 +0000
Subject: [PATCH] Fix UE5.1 crash: ditch FMemStack in DebugRenderSceneProxy

---
 Source/StevesUEHelpers/Private/StevesDebugRenderSceneProxy.cpp | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Source/StevesUEHelpers/Private/StevesDebugRenderSceneProxy.cpp b/Source/StevesUEHelpers/Private/StevesDebugRenderSceneProxy.cpp
index eda4ba4..adc114f 100644
--- a/Source/StevesUEHelpers/Private/StevesDebugRenderSceneProxy.cpp
+++ b/Source/StevesUEHelpers/Private/StevesDebugRenderSceneProxy.cpp
@@ -73,7 +73,7 @@ void FStevesDebugRenderSceneProxy::GetDynamicMeshElements(const TArray<const FSc
 
 				// Parent caches these (only within this function) but let's assume that's not worth it. Will people really
 				// have lots of meshes with a shared colour in this single context to make it worth it?
-				const auto MatRenderProxy = new(FMemStack::Get()) FColoredMaterialRenderProxy(GEngine->WireframeMaterial->GetRenderProxy(), Mesh.Color);
+				const auto MatRenderProxy = new FColoredMaterialRenderProxy(GEngine->WireframeMaterial->GetRenderProxy(), Mesh.Color);
 				FDynamicMeshBuilderSettings Settings;
 				Settings.bWireframe = true;
 				Settings.bUseSelectionOutline = false;