From aa9799a63b0b9c413e5f1431a299d41275648987 Mon Sep 17 00:00:00 2001
From: Nicholas Van Sickle <nvsickle@amazon.com>
Date: Mon, 13 Dec 2021 15:05:17 -0800
Subject: [PATCH] Use the high perf allocator for DomValueWriter

Signed-off-by: Nicholas Van Sickle <nvsickle@amazon.com>
---
 Code/Framework/AzCore/AzCore/DOM/DomValueWriter.h | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/Code/Framework/AzCore/AzCore/DOM/DomValueWriter.h b/Code/Framework/AzCore/AzCore/DOM/DomValueWriter.h
index 7430ff910b..488535ace6 100644
--- a/Code/Framework/AzCore/AzCore/DOM/DomValueWriter.h
+++ b/Code/Framework/AzCore/AzCore/DOM/DomValueWriter.h
@@ -56,17 +56,17 @@ namespace AZ::Dom
 
         struct ValueBuffer
         {
-            AZStd::vector<Value> m_elements;
-            AZStd::vector<AZStd::pair<AZ::Name, Value>> m_attributes;
+            Array::ContainerType m_elements;
+            Object::ContainerType m_attributes;
         };
 
         ValueBuffer& GetValueBuffer();
 
         Value& m_result;
         // Stores info about the current value being processed
-        AZStd::stack<ValueInfo> m_entryStack;
+        AZStd::stack<ValueInfo, AZStd::deque<ValueInfo, AZStdAlloc<ValueAllocator>>> m_entryStack;
         // Provides temporary storage for elements and attributes to prevent extra heap allocations
         // These buffers persist to be reused even as the entry stack changes
-        AZStd::vector<ValueBuffer> m_valueBuffers;
+        AZStd::vector<ValueBuffer, AZStdAlloc<ValueAllocator>> m_valueBuffers;
     };
 } // namespace AZ::Dom