No, all other programs and tasks are closed, and will always happen after a fresh restart of the computer.

So have just installed my RTX 4090 and used the same scene which has varied from hours to complete or just 8 or so minutes. With the 4090, I rendered the scene multiple times which took less than 3 minutes. Now all of a sudden without changing anything, it has slowed down to a speed predicting it will take 3 hours to complete. With the 4090 with tiling set to 128, it would complete 3-4 tiles per second. Now it is taking 10+ seconds to do each tile.

@Thomas Dinges (dingto) Just tested and the issue is the same in 2.93 as well as 3.3.1

In T90011#1235906, @Richard Antalik (ISS) wrote:

@David Cherrie (davidcherrie) Hi, just wondering about status of this report, did you manage to identify the issue and can you share sample file?

I have isolated the issue to a linked geometry node. Got 23 frames rendered in the original problematic file before the System is out of GPU Memory. After stopping the render and trying to restart the render, on the first frame I get the GPU Memory message.

I have been trying on a file that I am able to share but yesterday had it rendering for 6 hours using Cycles at 1920x1080 and got up to 590 frames with no issues.

I can't actually upload the file due to NDA. However working on another file (which I also can't share) which is totally seperate, after rendering multiple 4K images out over the course of working on the file for a few hours. I got the error message "System out of GPU memory". I escaped, didn't close the file but tried to re-render, same message came up and wouldn't start. I then went from LookDev to the internal shade view (forget what its called), pressed render then it started rendering.

Yes I was able to re-render after starting the render again. First time it got to frame 155 and then continued on from that frame which it got to frame 206. I would have expected it to have rendered another 155 frames but it only rendered 51.

In T71147#817871, @Clément Foucault (fclem) wrote:

@David Cherrie (davidcherrie) Run blender from command line using blender --debug-gpu-force-workarounds

See https://docs.blender.org/manual/en/dev/advanced/command_line/launch/macos.html

In T71147#817719, @Clément Foucault (fclem) wrote:

Can anyone try to run blender with --debug-gpu-force-workarounds and reproduce the bug?

This is an issue with 2.81 and is well known about where Eevee stops rendering.

@Omar Rahim (3Omar9) I have the issue on a 2017 MacBook Pro 15inch Touch and with a 2016 MacBook Pro 15inch Retina. 2017 happens on Mojave and Catalina and the 2016 happens on High Sierra.

VRAM would certainly make sense. I just used the factory default 2.81.16 (one released 13th November) and created a metaball, added a multi-resolution modifier with 3 sub-divisions. Sculpted a bit, turned on Render viewport, added a second lamp into the scene and then selected the other lamp, and then the metaball disappeared.

Issue still happening in v2.81.16