Blender 3.5.1 Crashes When Rendering from a Motion Tracked Project With Multiple Composite Layers

Support Technical Support
1

So, I have been using Blender for years but never tried the motion tracking till just yesterday. I got a nice scene built and started to render it, using cycles (tried both experimental and supported with GPU compute). It goes anywhere from 5 to 45 frames and them it either crashes or freezes. Thankfully i rendered to jpg, so i can pick up where it left off and go another 5 to 45 frames before it does it again.

I tried changing from Optix to Cuda. I even unchecked my CPU and only left my GPU to render (I have both checked before, which has always worked fine in the past).

Now, before any of you get ahead of yourself in answering, I have a beast of a computer.

AMD Ryzen 9 5900X

64GB DDR4

RTX 4070 TI

Windows 11 Pro

Running the latest stable Nvidea studio drivers.

Now with that out of the way, . . . I have tried plenty of troubleshooting steps. I tried to convert the tracking data to keyframes, thinking it was the trackers that caused it. But still no changes.

I also thought it could be some sort of memory problem so I reduced the tiling to only 512 (even though I had 12gb vram to spare).

I want the scene to match the graininess of the video, so I am rendering only at 128 samples.

I did notice when you create a floor for the scene using the motion tracking bit, it makes a composite layer just for the shadows and renders that separately. And no matter what I try, I can’t seem to get any other object to work as a shadow catcher on that layer. I know that is a side note, but kinda weird.

Now, for some reason, it will sometimes render as many as 20 to 40 frames before crashing, but other times it might just render 5. And it either just closes the program, or it will freeze and lock up my computer for a time and crash the drivers. The most recent one caused windows to lock blender saying “the Blender.exe application has been blocked from accessing graphics hardware”, after the last crash.

I am just stumped. I have rendered countless hundreds of scenes and hours upon hours of render time and never seen blender crash like this before. I can even set my computer up to render for 8 hours and it always has done fine.

I am water cooled and never get GPU temps above 58 C.

Any thoughts? I would add the blend file but can’t seem to add it here. Once I figure that out, I will add it.

2

The symptoms I experienced had problems ending during rendering, even if they were 10% or 20% or less.

The cause was low memory. :joy:
(Exit when GPU memory + system shared memory is out of range)

3

Good morning. Welcome to the BA forums.

Find your crash logs - both blender and windows. They should give some useful info.
The tracking data is tiny memory wise.

I have never had a crash while rendering out a tracked scene. Not since tracking came out years ago and the computer was an antique. Not even when saving as .exr files.

The only thing that springs to mind is you have introduced a loop accidentally in the compositing / tracking setup.

There is always the chance the file is corrupted. Unfortunately that’s a fact of life.

You can always share the file via cloud and drop the link here. There is a file size limit here so many users have to do that.
Its drag n drop into the comment, or use the icons in the comment to upload a file.