Potential Memory Corruption in Release Build (#3559)
* Potential Memory Corruption in Release Build Signed-off-by: Esteban Papp <81431996+amznestebanpapp@users.noreply.github.com> * @lumberyard-employee-dm suggested code Signed-off-by: Esteban Papp <81431996+amznestebanpapp@users.noreply.github.com> * warnings as errors found in VS2022 Signed-off-by: Esteban Papp <81431996+amznestebanpapp@users.noreply.github.com> * simplifying some strucutres used and fixing a bug Signed-off-by: Esteban Papp <81431996+amznestebanpapp@users.noreply.github.com> * some unused fixes for VS2022 Signed-off-by: Esteban Papp <81431996+amznestebanpapp@users.noreply.github.com> * fix for other platforms Signed-off-by: Esteban Papp <81431996+amznestebanpapp@users.noreply.github.com> * fixes check used in unit tests to be case-insensitive fixes memory leaks/invalid memory operations in AWSCore tests Signed-off-by: Esteban Papp <81431996+amznestebanpapp@users.noreply.github.com>
This commit is contained in:
@@ -1821,7 +1821,6 @@ namespace UnitTest
|
||||
|
||||
Api::InitializeAsUnitTriangle(*m_whiteBox);
|
||||
|
||||
const auto vertexCount = Api::MeshVertexCount(*m_whiteBox);
|
||||
const auto vertexHandles = Api::MeshVertexHandles(*m_whiteBox);
|
||||
const auto vertexPositions = Api::MeshVertexPositions(*m_whiteBox);
|
||||
|
||||
|
||||
Reference in New Issue
Block a user