LuxCoreRender Forums

just a couple of time now that i get a bug while animating with 2.4 Cuda build. Each 48 frames i get an error "clenqueuwritebuffer". And render stop.
look like the gpu go out of memory. but this is no matter the scene size. as it happen now with a small size scene.

will try to reproduce it with a simpler scene for debugging.

It is likely to be some kind of memory leak with CUDA (it would be useful to understand if it happens only with CUDA or also with OpenCL).

I also get this error, but when this happens, the computer needs a reboot.
After a reboot here it works - if the GPU Memory is large enough.
Here its like that, that even a restart of Blender will not fix the problem.
Only a restart of the computer will fix the problem.

Theo_Gottwald wrote: ↑Wed May 13, 2020 9:58 pm I also get this error, but when this happens, the computer needs a reboot.
After a reboot here it works - if the GPU Memory is large enough.
Here its like that, that even a restart of Blender will not fix the problem.
Only a restart of the computer will fix the problem.

This really sounds more like a driver bug than an application bug.

I can agree to that, because also Cycles sometimes just quits rendering.
I have 2x GTX 1080 currently. But seeing the rendertime I am working on something with RTX
Just nor sure if i should take it for that price
https://www.alibaba.com/product-detail/ ... 723bQTMzZ8
To night i had an animation rendering. Just at frame 37 it stopped rendering with this error.
If you want to try, download it here:


This one:
42 MB Scene.
This one is also for download.
42 MB Scene.

I still have this error plus blender crash from time to time each 48 frames render.

Btw 150§ for a RTX 2080 TI is pretty strange. would like to see how this end up

I don't know if it's the same bug, but I also experienced an out-of-memory error rendering an animation on my own scene. (Apologies, I did not capture the exact error message)

I tried rendering again, and Blender crashed. It seems the memory became freed at that point. I loaded Blender up and ran a few frames again with Process Explorer open, and noticed this:
A couple seconds before each frame starts rendering, there is a little step up in the VRAM used, and it does not go down after the rendering finishes. The increase in VRAM seems to occur right around the instant this is printed in the console:
Is it weird that it does the BVH and compilation twice? I do have 2 RTX 2080 Ti so I suppose that's related. But I wonder if only 1 of them is being freed after the render?

I'll try some more tests (1 GPU only... CPU only...) and see what happens...

I'm using Blender 2.83 beta with latest daily BlendLuxCore (20b0093) on Windows 10. nVIDIA GeForce Game Ready Driver 441.66. Exact hardware in my signature.

Edit: CPU-only gives no issues. Running on a single GPU gives the same problem as shown above (except that it only does the BVH and compilation once), and when the memory amount reaches the max, Blender crashes and closes instantly.

Edit 2: I get the same result in Blender 2.82a. Just before each successive frame, the memory usage seems to go up around 155mb (between approx. 154mb and 167mb; sample size: about 12 frames)

Edit 3: Increase seems relatively constant at about 155mb, even when varying the render resolution and rendering a completely different .blend file

Edit 4: Finally figured out why CUDA wasn't working. nvrtc64_101_0.dll is missing from the BlendLuxCore-latest-win64.zip! Managed to find a copy from a previous CUDA-specific build. Now CUDA is working, and the memory gets freed after a render. So maybe it's just an OpenCL specific problem right now?

Edit 5: Ha, the DLL is now back in the new daily build.

Edit 6: Decided to test it - switched from CUDA back to OpenCL and rendered a few frames. The difference is quite noticeable:

This issue is a real pain. Yesterday night i had to wake up more than 10 Times to relaunch a 1000 frames test animation.
Any solution will be welcome.

Sharlybg wrote: ↑Tue Jun 02, 2020 9:11 pm This issue is a real pain. Yesterday i had to wake more than 10 Times to relaunch a 1000 frames test animation.
Any solution will be welcome.

Ouch.

If there is a possibility to use CUDA instead of OpenCL, I might suggest that?

Otherwise, try rendering in small batches from the CLI.
etc. for however many frames you have

You can paste those all into a batch file (e.g. render.cmd) and it should basically run unattended.

If there is a possibility to use CUDA instead of OpenCL, I might suggest that?

Had the same problem with CUDA before so i didn't test it. But with the new unified package CUDA work just fine

You litterally save me thanks.