So, is it a CUDA-only problem ?
Opencl clenqueuwritebuffer bug
Forum rules
Please upload a testscene that allows developers to reproduce the problem, and attach some images.
Please upload a testscene that allows developers to reproduce the problem, and attach some images.
Re: Opencl clenqueuwritebuffer bug
On my side i get this error solved by switching from Opencl to CUDA but with lastest unified build.So, is it a CUDA-only problem ?
Re: Opencl clenqueuwritebuffer bug
So it is a OpenCL problem ?
Re: Opencl clenqueuwritebuffer bug
i can probably say today that it is a opencl bug only now.So it is a OpenCL problem ?
Re: Opencl clenqueuwritebuffer bug
The problem only occurred for me with OpenCL in the unified build.
AMD Ryzen Threadripper PRO 5995WX 64-Cores | 2x Gigabyte RTX 4090 Gaming OC
ASUS Pro WS WRX80E-SAGE SE WIFI | 256GB Kingston Server Premier ECC Unbuffered DDR4
ASUS Pro WS WRX80E-SAGE SE WIFI | 256GB Kingston Server Premier ECC Unbuffered DDR4
Re: Opencl clenqueuwritebuffer bug
Btw it is such a pleasure to see luxcore render 1000 frames one after one without complaining. I feel so much peace. Will sleep happier tjis night. I have already 1055/1111 frames done currently.
Thanks for this beauty
Re: Opencl clenqueuwritebuffer bug
The problem is easy to replicate but it starts to smell like a NVIDIA driver bug. I have modified the OpenCL code so it should be pretty much impossible to have memory leak across different renderings but the problem is still there.
Is someone with an AMD GPU able to replicate the problem ?
Is someone with an AMD GPU able to replicate the problem ?