Undefined behaviour when initializing plan about vkfft HOT 3 CLOSED

Hello,

Originally I thought the user should zero-initialize the app struct before initialization as to not allow potential memory leaks (for example, if initializeVkFFT is called twice on the same app without freeing resources first).

Now I see that it is possible to add a full app memset to zero in the deleteVkFFT call and add a check for app bytes being zero in the initializeVkFFT call. This should be a better approach compared to setting configuration to zero.

I will add this in the next update.

Best regards,
Dmitrii

from vkfft.

Hi Dmitrii,

thank you for your reply. I am sorry, it was my mistake, I accidentally forgot to zero initialize the app object when I moved from OpenCL to CUDA. After zero initialization everything works fine.

Once again thank you very much.

Best regards,
David

from vkfft.

Hello,

I have added the checks for the app being zero and freeing the resources on being deleted. It will be soon merged into the master branch, thanks for suggesting it!

Best regards,
Dmitrii

from vkfft.