getMemoryWin32HandleKHR works once and not again.

[fast wraith]

I'm attempting to create a framebuffer for GL to draw to and Vk to read/present from. On Intel Graphics specifically getMemoryWin32HandleKHR() works as expected on the first call, returning a valid handle, importing to GL works just fine. It's only when I attempt to get a second handle from a separate texture I get odd behavior. Handle is null even though result is success? All further calls to getMemoryWin32HandleKHR() result in this same behavior with Result::eSuccess yet a null handle. Driver bug for intel? Or am I likely doing something wrong? Tested working on AMD and Nvidia drivers..

[rigid anchor]

There are many zeros there but not all of them are zeros. That value is not null.

[fast wraith]

Apologies this is the result of the first successful run, after this handle becomes nullptr