Cycles X cannot finish rendering a sequence #94383

New Issue

Ryota · 2021-12-26T01:56:11+01:00

Ryota commented

2021-12-26 01:56:11 +01:00

System Information
Operating system: Windows-10-10.0.19041-SP0 64 Bits
Graphics card: GeForce RTX 2060 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.89
32GB RAM

Blender Version
Broken: 3.0.0
Worked: 2.9.3

With Cycles X, the rendering gets stuck at random frames. It happens with any scene including the default scene.
I've updated the graphics card driver, tried reinstalling Blender, but they didn't work.

I brought down the sampling rate, turned off denoising etc which helped render more frames, but it always gets stuck before finishing all of it.
Looked into temp folder, but there was no error log.
I also tried using CUDA instead of OptiX, and also do CPU render, but they all get stuck at some point.
It doesn't seem it is using up all RAM or VRAM.

Exact steps for others to reproduce the error
I think it's specific to my set up and don't think that it's possible to reproduce it for other people. But for me, render any scene with about 100 frames and the render view will freeze at some point and crash.

Debug output and system information after rendering default scene, crash after 14 frames, no crash log found.
blender_debug_output.txt

blender_system_info.txt

**System Information** Operating system: Windows-10-10.0.19041-SP0 64 Bits Graphics card: GeForce RTX 2060 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.89 32GB RAM **Blender Version** Broken: 3.0.0 Worked: 2.9.3 With Cycles X, the rendering gets stuck at random frames. It happens with any scene including the default scene. I've updated the graphics card driver, tried reinstalling Blender, but they didn't work. I brought down the sampling rate, turned off denoising etc which helped render more frames, but it always gets stuck before finishing all of it. Looked into temp folder, but there was no error log. I also tried using CUDA instead of OptiX, and also do CPU render, but they all get stuck at some point. It doesn't seem it is using up all RAM or VRAM. **Exact steps for others to reproduce the error** I think it's specific to my set up and don't think that it's possible to reproduce it for other people. But for me, render any scene with about 100 frames and the render view will freeze at some point and crash. Debug output and system information after rendering default scene, crash after 14 frames, no crash log found. [blender_debug_output.txt](https://archive.blender.org/developer/F12778305/blender_debug_output.txt) [blender_system_info.txt](https://archive.blender.org/developer/F12778304/blender_system_info.txt)

Ryota commented

2021-12-26 01:56:11 +01:00

Added subscriber: @syn-crow

Ryota commented

2021-12-27 06:41:07 +01:00

CrashLog.txt

This is the last bit of log when I start the Blender in Debug mode and let it render until it stops working.

[CrashLog.txt](https://archive.blender.org/developer/F12777425/CrashLog.txt) This is the last bit of log when I start the Blender in Debug mode and let it render until it stops working.

Garek commented

2021-12-27 07:49:19 +01:00

Added subscriber: @Garek

Garek commented

2021-12-27 07:49:19 +01:00

Changed status from 'Needs Triage' to: 'Needs User Info'

Garek commented

2021-12-27 07:49:19 +01:00

Hi, thanks for the report. Does it happens with latest 3.1.0 alpha build?
https://builder.blender.org/download/daily/

Hi, thanks for the report. Does it happens with latest 3.1.0 alpha build? https://builder.blender.org/download/daily/

Ryota commented

2021-12-27 08:48:31 +01:00

Yes, it crashed on the second frame. For that one, I had the sampling to 100 and turned off the noise threshold, and had Optix Albedo Denoise.

Garek commented

2021-12-27 12:39:39 +01:00

Can you check if it's only Cycles, or EEVEE/Workbench is also affected?

For testing purposes it's better to simplify file as much as possible to rule out specific features. Using default scene is a good choice. While in default scene try File -> Defaults -> Load Factory Settings. That should rule out any non-standard add-ons.

Can you check if it's only Cycles, or EEVEE/Workbench is also affected? For testing purposes it's better to simplify file as much as possible to rule out specific features. Using default scene is a good choice. While in default scene try `File` -> `Defaults` -> `Load Factory Settings`. That should rule out any non-standard add-ons.

Ryota commented

2021-12-27 19:32:45 +01:00

EEVEE and Workbench seem to work fine.

I loaded the default setting, but with Cycles it got stuck half way rendering the first frame and it stopped. And that's just a default scene with a cube with no animation whatsoever.

EEVEE and Workbench seem to work fine. I loaded the default setting, but with Cycles it got stuck half way rendering the first frame and it stopped. And that's just a default scene with a cube with no animation whatsoever.

Garek commented

2021-12-27 20:27:49 +01:00

Can you run blender_debug_gpu.cmd and provide debug output along with crash log?

Can you run `blender_debug_gpu.cmd` and provide debug output along with crash log?

Ryota commented

2021-12-27 21:06:11 +01:00

blender_debug_output.txt

blender_system_info.txt

Here are the logs. It managed to render up to 14 frames and then it got stuck and stopped at 15. The scene was just a default cube with no animation. There was no crash log that I could see in the temp folder.

[blender_debug_output.txt](https://archive.blender.org/developer/F12778305/blender_debug_output.txt) [blender_system_info.txt](https://archive.blender.org/developer/F12778304/blender_system_info.txt) Here are the logs. It managed to render up to 14 frames and then it got stuck and stopped at 15. The scene was just a default cube with no animation. There was no crash log that I could see in the temp folder.

Garek commented

2021-12-28 06:14:25 +01:00

Changed status from 'Needs User Info' to: 'Needs Triage'

Garek commented

2021-12-28 06:14:25 +01:00

Thanks. I don't see anything strange in particular... Just a wild guess, check if your C drive have enough free space. When rendering Blender writes frames in temp folder on C drive.

Meanwhile I'll tag it as unconfirmed since there is high chance it's computer configuration, also change status since information is provided and so others can take a look.

Thanks. I don't see anything strange in particular... Just a wild guess, check if your C drive have enough free space. When rendering Blender writes frames in `temp` folder on C drive. Meanwhile I'll tag it as unconfirmed since there is high chance it's computer configuration, also change status since information is provided and so others can take a look.

Ryota commented

2021-12-28 06:39:49 +01:00

I don't think it's the disk space. I have about 700GB of free space in my C drive, but it's still freezing up.

Ryota commented

2021-12-28 21:29:54 +01:00

As the last hail Mary, I updated to Windows 11, and that seems to have worked.

I loaded up my scene that it could never render completely and put the samples to 100 and used OpenImageDenoise.
I was able to render all frames.

Update: With Noise Threshold on, it still does crash, but at least it can render without it.

Thank you for looking into this Garek.

As the last hail Mary, I updated to Windows 11, and that seems to have worked. I loaded up my scene that it could never render completely and put the samples to 100 and used OpenImageDenoise. I was able to render all frames. Update: With Noise Threshold on, it still does crash, but at least it can render without it. Thank you for looking into this Garek.

Ryota commented

2021-12-29 02:23:53 +01:00

Now I am suspecting that it has something to do with the Render window. When I minimize that window, I can throw any denoiser settings at it (including Noise Threshold and Optix denoiser) and it can render the sequence no problem. It's only when I leave the window open, the render gets stuck.

Obviously now that I know there is a work-around to finish rendering, it's much less of a priority, but would be nice to know why this is happening at some point.

Now I am suspecting that it has something to do with the Render window. When I minimize that window, I can throw any denoiser settings at it (including Noise Threshold and Optix denoiser) and it can render the sequence no problem. It's only when I leave the window open, the render gets stuck. Obviously now that I know there is a work-around to finish rendering, it's much less of a priority, but would be nice to know why this is happening at some point.

Garek commented

2021-12-29 15:16:12 +01:00

In #94383#1279567, @syn-crow wrote:
Now I am suspecting that it has something to do with the Render window. When I minimize that window, I can throw any denoiser settings at it (including Noise Threshold and Optix denoiser) and it can render the sequence no problem. It's only when I leave the window open, the render gets stuck.

So does Blender crash or Render window closes? Now that I recall debug output I suspect the latter.

What happens with other render display types?

> In #94383#1279567, @syn-crow wrote: > Now I am suspecting that it has something to do with the Render window. When I minimize that window, I can throw any denoiser settings at it (including Noise Threshold and Optix denoiser) and it can render the sequence no problem. It's only when I leave the window open, the render gets stuck. So does Blender crash or Render window closes? Now that I recall debug output I suspect the latter. What happens with other render display types? ![image.png](https://archive.blender.org/developer/F12780511/image.png)

Ryota commented

2021-12-29 17:38:43 +01:00

Keep User Window is the only one that works. For everything else, it just crashes after a few frames (I have all the denoising on).
When it crashes, it just stops in the middle of sampling and goes silent. When I click on the window, it just says Blender stopped responding and the window turns pale white.
This would be the same if I start rendering with the window minimized and then click on the window to enlarge it. At that point, after rendering a few more frames and it freezes.

Keep User Window is the only one that works. For everything else, it just crashes after a few frames (I have all the denoising on). When it crashes, it just stops in the middle of sampling and goes silent. When I click on the window, it just says Blender stopped responding and the window turns pale white. This would be the same if I start rendering with the window minimized and then click on the window to enlarge it. At that point, after rendering a few more frames and it freezes. ![Screenshot 2021-12-29 093250.png](https://archive.blender.org/developer/F12780722/Screenshot_2021-12-29_093250.png)

Richard Antalik commented

2022-02-02 03:17:34 +01:00

Added subscriber: @iss

Richard Antalik commented

2022-02-02 03:17:34 +01:00

Changed status from 'Needs Triage' to: 'Needs User Info'

Richard Antalik commented

2022-02-02 03:17:34 +01:00

@syn-crow Can you upload sample file? This looks like valid issue, but without sample file I don't think I will be able to reproduce. Also did you check any later development versions?

Ryota commented

2022-02-02 03:23:34 +01:00

It's not scene specific. I can just open Blender with default scene, change to Cycles and hit render right away, and it will still crash if I have render view opened.

I will try the 3.1 beta and let you know.

It's not scene specific. I can just open Blender with default scene, change to Cycles and hit render right away, and it will still crash if I have render view opened. I will try the 3.1 beta and let you know.

Richard Antalik commented

2022-02-03 03:45:04 +01:00

Thanks for update, that I definitely can't reproduce. Also did not see request to try updating GPU drivers, can you check of that helps too?

Richard Antalik commented

2022-04-12 21:09:04 +02:00

Changed status from 'Needs User Info' to: 'Archived'

Richard Antalik closed this issue

2022-04-12 21:09:04 +02:00

Richard Antalik commented

2022-04-12 21:09:04 +02:00

No activity for more than a week. As per the tracker policy we assume the issue is gone and can be closed.

Thanks again for the report. If the problem persists please open a new report with the required information.

No activity for more than a week. As per the tracker policy we assume the issue is gone and can be closed. Thanks again for the report. If the problem persists please open a new report with the required information.

Sign in to join this conversation.

No Label

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Cycles X cannot finish rendering a sequence #94383