Blender Rendering Crash by version 3.1.2 #97064

New Issue

WangYun · 2022-04-05T10:11:07+02:00

WangYun commented

2022-04-05 10:11:07 +02:00

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
SV.blend

Here is the error log
CY-MC-001.crash.txt

**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 [SV.blend](https://archive.blender.org/developer/F12977395/SV.blend) Here is the error log [CY-MC-001.crash.txt](https://archive.blender.org/developer/F12973769/CY-MC-001.crash.txt)

WangYun commented

2022-04-05 10:11:07 +02:00

Added subscriber: @fan_tangCK

WangYun changed title from ~~Blender Rendering Crash by version 3.2.1~~ to Blender Rendering Crash by version 3.1.2

2022-04-05 10:11:19 +02:00

Omar Emara commented

2022-04-05 10:14:34 +02:00

Added subscriber: @OmarEmaraDev

Omar Emara commented

2022-04-05 10:14:34 +02:00

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

Omar Emara commented

2022-04-05 10:14:34 +02:00

Does this happen with factory settings? File > Defaults > Load Factory Settings.

WangYun commented

2022-04-05 10:14:35 +02:00

PS:I am using the CYCLES rendering engine. Denoise using OPTIX, CYCLES rendering acceleration using OPTIX

WangYun commented

2022-04-05 10:24:17 +02:00

In #97064#1335589, @OmarEmaraDev wrote:
Does this happen with factory settings? File > Defaults > Load Factory Settings.

I just tested the rendering with factory settings and it still crashed at around 100 frames

> In #97064#1335589, @OmarEmaraDev wrote: > Does this happen with factory settings? File > Defaults > Load Factory Settings. I just tested the rendering with factory settings and it still crashed at around 100 frames

WangYun commented

2022-04-05 12:53:06 +02:00

@OmarEmaraDev

Omar Emara commented

2022-04-05 13:59:46 +02:00

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?

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?

WangYun commented

2022-04-05 15:39:58 +02:00

In #97064#1335880, @OmarEmaraDev wrote:
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

> In #97064#1335880, @OmarEmaraDev wrote: > 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

WangYun commented

2022-04-05 15:41:28 +02:00

That can be considered a bug, even if it has been accidentally solved, but still hope that a comprehensive solution

WangYun commented

2022-04-06 00:58:42 +02:00

@OmarEmaraDev
I asked a person with blender version 2.83 to 3.0 has always had this bug

In #97064#1335980, @fan_tangCK wrote:

In #97064#1335880, @OmarEmaraDev wrote:
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

@OmarEmaraDev I asked a person with blender version 2.83 to 3.0 has always had this bug > In #97064#1335980, @fan_tangCK wrote: >> In #97064#1335880, @OmarEmaraDev wrote: >> 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

Omar Emara commented

2022-04-06 08:41:00 +02:00

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?

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?

WangYun commented

2022-04-06 08:42:24 +02:00

In #97064#1336354, @OmarEmaraDev wrote:
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?

Yes,I just rendering to a movie

> In #97064#1336354, @OmarEmaraDev wrote: > 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? Yes,I just rendering to a movie

Omar Emara commented

2022-04-06 08:47:38 +02:00

Is it possible to attach a simplified version of this file?

WangYun commented

2022-04-06 08:55:06 +02:00

In #97064#1336361, @OmarEmaraDev wrote:
Is it possible to attach a simplified version of this file?

Try to render using Factory Settings
SV.blend

> In #97064#1336361, @OmarEmaraDev wrote: > Is it possible to attach a simplified version of this file? Try to render using Factory Settings [SV.blend](https://archive.blender.org/developer/F12977395/SV.blend)

Omar Emara commented

2022-04-06 09:25:03 +02:00

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?

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?

WangYun commented

2022-04-06 10:33:20 +02:00

Unsurprisingly it still crashes, even with cmd rendering

In #97064#1336378, @OmarEmaraDev wrote:
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?

![image.png](https://archive.blender.org/developer/F12977656/image.png) Unsurprisingly it still crashes, even with cmd rendering > In #97064#1336378, @OmarEmaraDev wrote: > 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?

WangYun commented

2022-04-06 10:36:14 +02:00

@OmarEmaraDev
Here is log{F12977660}

@OmarEmaraDev Here is log{[F12977660](https://archive.blender.org/developer/F12977660/CY-MC-001.crash.txt)}

Omar Emara commented

2022-04-06 10:36:24 +02:00

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

Omar Emara commented

2022-04-06 10:36:24 +02:00

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.

WangYun commented

2022-04-06 10:42:38 +02:00

This comment was removed by @fan_tangCK

*This comment was removed by @fan_tangCK*

WangYun commented

2022-04-06 10:48:28 +02:00

@OmarEmaraDev
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.

In #97064#1336477, @OmarEmaraDev wrote:
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.

@OmarEmaraDev 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. > In #97064#1336477, @OmarEmaraDev wrote: > 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.

WangYun commented

2022-04-06 12:38:41 +02:00

@OmarEmaraDev

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

@OmarEmaraDev ![image.png](https://archive.blender.org/developer/F12977902/image.png) 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 commented

2022-04-08 07:03:56 +02:00

@OmarEmaraDev

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)?

In #97064#1336591, @fan_tangCK wrote:
@OmarEmaraDev

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

@OmarEmaraDev 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)? > In #97064#1336591, @fan_tangCK wrote: > @OmarEmaraDev > ![image.png](https://archive.blender.org/developer/F12977902/image.png) > 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

Omar Emara commented

2022-04-08 08:02:58 +02:00

@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.

WangYun commented

2022-04-08 08:09:20 +02:00

In #97064#1337761, @OmarEmaraDev wrote:
@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.

> In #97064#1337761, @OmarEmaraDev wrote: > @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.

Richard Antalik commented

2022-06-10 19:09:01 +02:00

Added subscriber: @iss

Richard Antalik commented

2022-06-10 19:09:01 +02:00

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

Richard Antalik commented

2022-06-10 19:09:02 +02:00

@fan_tangCK Can you check if this is still an issue in latest alpha from https://builder.blender.org/download/daily/?

WangYun commented

2022-06-22 13:36:18 +02:00

In #97064#1372467, @iss wrote:
@fan_tangCK Can you check if this is still an issue in latest alpha from https://builder.blender.org/download/daily/?

@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

> In #97064#1372467, @iss wrote: > @fan_tangCK Can you check if this is still an issue in latest alpha from https://builder.blender.org/download/daily/? @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

Richard Antalik commented

2022-06-22 16:28:59 +02:00

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

Richard Antalik commented

2022-06-22 16:28:59 +02:00

Thanks for checking, I am not familiar with e-cycles branch.

WangYun commented

2022-06-25 05:31:51 +02:00

CY-MC-001.crash.txt
@iss Rendering crashes after a while, this crash log

In #97064#1378604, @iss wrote:
Thanks for checking, I am not familiar with e-cycles branch.

[CY-MC-001.crash.txt](https://archive.blender.org/developer/F13227515/CY-MC-001.crash.txt) @iss Rendering crashes after a while, this crash log > In #97064#1378604, @iss wrote: > Thanks for checking, I am not familiar with e-cycles branch.

Maxime Sanchez commented

2022-08-01 00:50:08 +02:00

Added subscriber: @Maxime66410

Maxime Sanchez commented

2022-08-01 00:50:08 +02:00

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

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 ![image.png](https://archive.blender.org/developer/F13328080/image.png)

Philipp Oeser commented

2022-08-18 12:35:37 +02:00

Added subscriber: @lichtwerk

Philipp Oeser commented

2022-08-18 12:35:37 +02:00

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

Philipp Oeser commented

2022-08-18 12:35:37 +02:00

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?

In #97064#1335980, @fan_tangCK wrote:

In #97064#1335880, @OmarEmaraDev wrote:
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

Since you mentioned this workaround, does it help disabling the Sequencer completely?

{F13400015 size=full}

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? > In #97064#1335980, @fan_tangCK wrote: >> In #97064#1335880, @OmarEmaraDev wrote: >> 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 Since you mentioned this workaround, does it help disabling the Sequencer completely? {[F13400015](https://archive.blender.org/developer/F13400015/image.png) size=full}

Philipp Oeser commented

2022-09-06 13:47:04 +02:00

poke ^

WangYun commented

2022-09-09 11:58:19 +02:00

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

WangYun closed this issue

2022-09-09 11:58:19 +02:00

WangYun self-assigned this 2022-09-09 11:58:19 +02:00

WangYun commented

2022-09-09 11:58:19 +02:00

In #97064#1413011, @lichtwerk wrote:
poke ^

I'm sorry to reply now, but I'm currently unable to reproduce this problem.

> In #97064#1413011, @lichtwerk wrote: > poke ^ I'm sorry to reply now, but I'm currently unable to reproduce this problem.

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

Blender Rendering Crash by version 3.1.2 #97064