STATUS_HEAP_CORRUPTION on Windows 11 ARM Debug64 tests
On Windows 11 ARM machines, which are routinely tested for Release64 builds but not Debug64 builds, shows a failure when attempting to execute tests after building in Debug64: http://tcubuser.lunarg.localdomain:8080/view/Manual/job/manual-Vulkan-ExtensionLayer/44/console
INFO: testing extension layer tests...
INFO: set VK_LAYER_PATH=C:\j\mvel0\Vulkan-ExtensionLayer\dbuild\layers\Debug
INFO: cd C:\j\mvel0\Vulkan-ExtensionLayer
INFO: executing #8: C:\j\mvel0\Vulkan-ExtensionLayer\dbuild\install\bin\vk_extension_layer_tests.exe --gtest_catch_exceptions=0
ERROR: execute() call failed after 0.89 seconds (0.89 seconds): returncode=3221226356 (0xc0000374=STATUS_HEAP_CORRUPTION); execution log index: 8, working directory: C:\j\mvel0\Vulkan-ExtensionLayer
ERROR: ----stdout---------------------------------------------------
[==========] Running 25 tests from 4 test suites.
[----------] Global test environment set-up.
[----------] 9 tests from ShaderObjectTest
[ RUN ] ShaderObjectTest.VertFragShader
ERROR: -------------------------------------------------------------
ERROR: FAIL during test after 0.89 seconds (0.89 seconds) with execute(C:\j\mvel0\Vulkan-ExtensionLayer\dbuild\install\bin\vk_extension_layer_tests.exe --gtest_catch_exceptions=0) failed after 0.89 seconds (0.89 seconds) with returncode=3221226356 (0xc0000374=STATUS_HEAP_CORRUPTION)
INFO: Test run complete after 1.65 minutes (98.99 seconds)
For a comparison, a test of the same commit but with a Release64 build passes: http://tcubuser.lunarg.localdomain:8080/view/Manual/job/manual-Vulkan-ExtensionLayer/45/console
INFO: -- Starting test
INFO: testing that this Windows machine is configured correctly...
INFO: testing extension layer tests...
INFO: set VK_LAYER_PATH=C:\j\mvel0\Vulkan-ExtensionLayer\build\layers\Release
INFO: cd C:\j\mvel0\Vulkan-ExtensionLayer
INFO: executing #8: C:\j\mvel0\Vulkan-ExtensionLayer\build\install\bin\vk_extension_layer_tests.exe --gtest_catch_exceptions=0
INFO: Tests PASS
When this is resolved, please notify CI so we can add the Windows11-ARM Debug64 configuration to CI tests.
When this is resolved, please notify CI so we can add the Windows11-ARM Debug64 configuration to CI tests.
@johnzupin @lunarpapillo
I enabled the Windows11-ARM Debug64 configuration on the Jenkins Vulkan-ExtensionLayer tests: http://tcubuser.lunarg.localdomain:8080/job/Vulkan-ExtensionLayer/1073/
All pass, verifying the fix. Leaving this configuration enabled will allow us to detect the issue in the future.