System Information
Operating system:
Graphics card:RTX 3050Ti
RAM:16G
Blender Version
Broken: 3.1.2 , 2022-4-5, crash when rendering
Short description of error
When I rendered the export, a scene with more than 1000 frames crashed after about 160 frames of blender rendering. The memory and video memory usage is far from over the limit. Hope to get a solution.
Try to render using Factory Settings
Here is the error log
PS:I am using the CYCLES rendering engine. Denoise using OPTIX, CYCLES rendering acceleration using OPTIX
I just tested the rendering with factory settings and it still crashed at around 100 frames
Does this happen for this file only? If yes, might you be able to share a simplified version of it?
And does enabling Render > Lock Interface fix the issue?
I actually rendered with the Lock Interface turned on
But by accident, I found the solution, as follows.
The default blender memory cache limit is 4096
When changing it to 2048, the rendering goes smoothly
That can be considered a bug, even if it has been accidentally solved, but still hope that a comprehensive solution
@Omar Emara (OmarSquircleArt)
I asked a person with blender version 2.83 to 3.0 has always had this bug
Are you rendering in video sequencer then? Because the memory cache limit is only related to VSE as far as I know.
Are you rendering to an image sequence or a movie directly?
I see you are using Animation Nodes in that scene, which sometimes suffer from crashes like this, see https://github.com/JacquesLucke/animation_nodes/issues/1200.
Can you try the solution presented there and confirm that the crash happens because of Animation Nodes?
hmmm, then I am out of ideas. I can't replicate the issue after rendering 200 frames myself, but I am rendering on CPU and on a different system.
@Omar Emara (OmarSquircleArt)
According to the logs, it seems that the problem appears in the file tbbmalloc.dll.
I hope to find a developer who knows what this file is for and ask about it.
Does the ability to use OPTIX accelerated rendering have a big impact on my workflow, is there any solution for this (as shown on the picture using OPTIX accelerated rendering, it crashes after 200 frames)?
The real problem has been found, I just used OPTIX rendering instead of CUDA, OPTIX causes crashes, while using CUDA has rendered the whole video perfectly
@WangYun (fan_tangCK) OPTIX is typically faster, so rendering will likely be slower with CUDA. Though I suspect the issue is not specifically caused by OPTIX and this needs to be tried more thoroughly.
In the case of Factory Settings, OPTIX crashes after a certain number of frames and CUDA is very stable.
@WangYun (fan_tangCK) Can you check if this is still an issue in latest alpha from https://builder.blender.org/download/daily/?
@Richard Antalik (ISS)
Unfortunately, this problem still occurs in blender 3.2 (error log shows EXCEPTION_ACCESS_VIOLATION). But the weird thing is that this problem never occurs in the blender branch version e-cycles (E-Cycles_X_Pro_RTX_3.2_release_20220607_win). So I suspect it's a trunk version problem
Same with me.
it does not work from higher than 8K.
My configuration :
CPU : AMD Ryzen 7 2700x
GPU : NVIDIA GeForce RTX 2070
RAM : 32GB
Hm, that example file renders fine here with Optix in 3.1.2 (lowered samples, stopped at 250 frames).
blender eats ~1G RAM during rendering (some smaller spikes)
GPU eats 1.6G (with spikes at ~2.5G) during rendering
**System Information** Operating system: Linux-5.13.0-0.rc6.45.fc35.x86_64-x86_64-with-glibc2.34.9000 64 Bits Graphics card: NVIDIA GeForce GTX 970M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 495.44 version: 3.1.2, branch: master, commit date: 2022-03-31 17:40, hash: `rBcc66d1020c3b`
So I could not spot a memory leak on my side.
Does RAM usage /GPU memory usage slowly increase over the framerange?
Since you mentioned this workaround, does it help disabling the Sequencer completely?
