EEVEE: Crash if computation is too heavy for the system (TDR issue) #65223

New Issue

Andrew · 2019-05-28T08:54:17+02:00

Andrew commented

2019-05-28 08:54:17 +02:00

System Information
Operating system: Windows-10-10.0.17134 64 Bits
Graphics card: GeForce RTX 2080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 430.64

Blender Version
Broken: version: 2.80 (sub 72), branch: blender2.7, commit date: 2019-05-27 19:48, hash: 89207df722
Worked: (optional)

Short description of error
Any time I try to render an image sequence in any format in Eevee, it constantly crashes the whole program on the first frame. I was able to render before until I changed some camera location animations and adding a focusing animation. As well as changing the camera sensor size. I am rendering in 4K I have attached the log file.
blender_debug_output.txt

blender_system_info.txt

NebulaV2.blend

**System Information** Operating system: Windows-10-10.0.17134 64 Bits Graphics card: GeForce RTX 2080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 430.64 **Blender Version** Broken: version: 2.80 (sub 72), branch: blender2.7, commit date: 2019-05-27 19:48, hash: `89207df722` Worked: (optional) **Short description of error** Any time I try to render an image sequence in any format in Eevee, it constantly crashes the whole program on the first frame. I was able to render before until I changed some camera location animations and adding a focusing animation. As well as changing the camera sensor size. I am rendering in 4K I have attached the log file. [blender_debug_output.txt](https://archive.blender.org/developer/F7074082/blender_debug_output.txt) [blender_system_info.txt](https://archive.blender.org/developer/F7074083/blender_system_info.txt) [NebulaV2.blend](https://archive.blender.org/developer/F7076346/NebulaV2.blend)

Andrew commented

2019-05-28 08:54:17 +02:00

Added subscriber: @GemstoneStudios

blender-admin commented

2019-05-28 08:54:17 +02:00

#71689 was marked as duplicate of this issue

blender-admin commented

2019-05-28 08:54:17 +02:00

#70084 was marked as duplicate of this issue

Brecht Van Lommel commented

2019-05-28 11:03:18 +02:00

Added subscriber: @brecht

Brecht Van Lommel commented

2019-05-28 11:03:18 +02:00

We require an example .blend file to reproduce bugs.

Dalai Felinto commented

2019-05-28 21:53:40 +02:00

Added subscriber: @dfelinto

Dalai Felinto commented

2019-05-28 21:53:40 +02:00

It crashed here as well and I got to restart. It may be the high resolution of the render. Writing this down before I eventually have to restart the computer again.

Andrew commented

2019-05-28 22:04:51 +02:00

I have tried restarting it multiple times and it has still crashed. It rendered in 4K before I did the changes I described above. Could it be the camera sensor size or the focusing animation that could be causing issues?

Clément Foucault was assigned by Dalai Felinto

2019-05-28 22:43:35 +02:00

Dalai Felinto commented

2019-05-28 22:43:35 +02:00

(one or two restarts later ...)

We have a double locking going on here.

DRW_render_to_image() > DRW_opengl_render_context_enable() > engine_type->draw_engine->render_to_image()
And before we get to calling DRW_opengl_render_context_disable() we get a lock in DRW_opengl_context_enable_ex().

My blind guess is that rendering in a new window is part of the issue.

(one of the restarts messed with my internet on Linux, I will be back to it later)

*(one or two restarts later ...)* We have a double locking going on here. `DRW_render_to_image()` > `DRW_opengl_render_context_enable()` > `engine_type->draw_engine->render_to_image()` And before we get to calling `DRW_opengl_render_context_disable()` we get a lock in `DRW_opengl_context_enable_ex()`. My blind guess is that rendering in a new window is part of the issue. *(one of the restarts messed with my internet on Linux, I will be back to it later)*

Dalai Felinto commented

2019-05-28 23:26:40 +02:00

My blind guess is that rendering in a new window is part of the issue.

Not really the case. Anyways I will leave to Clément to figure out what is next here.

>My blind guess is that rendering in a new window is part of the issue. Not really the case. Anyways I will leave to Clément to figure out what is next here.

Dalai Felinto commented

2019-05-28 23:35:14 +02:00

Added subscriber: @Sergey

Dalai Felinto commented

2019-05-28 23:35:14 +02:00

Not sure if related, but I took the file, changed render size (1024x1024):

NebulaV3.blend

Now if I try to render the file above I get the following depsgraph assert when adding the scene node itself:
BLI_assert failed: //source/blender/depsgraph/intern/depsgraph.cc:121, add_id_node(), at '(id->tag & LIB_TAG_COPIED_ON_WRITE) == 0'

Full backtrace: P987

Not sure if related, but I took the file, changed render size (1024x1024): [NebulaV3.blend](https://archive.blender.org/developer/F7076837/NebulaV3.blend) Now if I try to render the file above I get the following depsgraph assert when adding the scene node itself: `BLI_assert failed: //source/blender/depsgraph/intern/depsgraph.cc:121, add_id_node(), at '(id->tag & LIB_TAG_COPIED_ON_WRITE) == 0'` Full backtrace: [P987](https://archive.blender.org/developer/P987.txt)

Clément Foucault was unassigned by Sergey Sharybin

2019-05-28 23:58:11 +02:00

Sergey Sharybin self-assigned this 2019-05-28 23:58:11 +02:00

Sergey Sharybin commented

2019-05-28 23:58:11 +02:00

Added subscriber: @fclem

Sergey Sharybin removed their assignment 2019-05-29 12:51:52 +02:00

Clément Foucault was assigned by Sergey Sharybin

2019-05-29 12:51:52 +02:00

Sergey Sharybin commented

2019-05-29 12:51:52 +02:00

The bug in depsgrapgh is now fixed.

File from Dalai seems to be rendering fine now. But the original file takes quite a bit to render. Not sure if it's something wrong in code or is just how the file is set up.

Crashes i couldn't reproduce so far after my fix, but would be cool if someone verifies this.

The bug in depsgrapgh is now fixed. File from Dalai seems to be rendering fine now. But the original file takes quite a bit to render. Not sure if it's something wrong in code or is just how the file is set up. Crashes i couldn't reproduce so far after my fix, but would be cool if someone verifies this.

Andrew commented

2019-05-29 22:27:48 +02:00

I tried rendering again with my 4K settings with the latest version of 2.8 today and it still crashes the whole program. 1080p and lower seen to work but I need to be rendering this particular project in 4K. If my last resort is to upscale it, I will, but that is something I would like to avoid.

Sergey Sharybin commented

2019-05-29 22:47:36 +02:00

@GemstoneStudios, if you're using buildbot.b.o then it doesn't have the fix yet.

Could also be GPU limitation or a driver bug. Are there any error messages printed to the console?

@GemstoneStudios, if you're using buildbot.b.o then it doesn't have the fix yet. Could also be GPU limitation or a driver bug. Are there any error messages printed to the console?

Andrew commented

2019-05-30 23:55:49 +02:00

I am able to render but I cannot have any render displays turned on. Anytime I try and use a view that shows the render, it crashes. It’s currently rendering the scene now. I noticed it gets hung up on the first frame to be rendered, but it starts speeding up after the first frame of the animation is completed.

Andrew commented

2019-05-31 01:53:45 +02:00

It crashed during the middle of the render. Here are the bug logs.

blender_system_info.txt

blender_debug_output.txt

It crashed during the middle of the render. Here are the bug logs. [blender_system_info.txt](https://archive.blender.org/developer/F7080434/blender_system_info.txt) [blender_debug_output.txt](https://archive.blender.org/developer/F7080435/blender_debug_output.txt)

Bodhi Jaksza commented

2019-06-03 20:35:35 +02:00

Added subscriber: @Jaksza

Clément Foucault commented

2019-06-05 12:43:48 +02:00

Ok it crashes because the rendering is too heavy (takes too much time to render). What is taking the most time is the Depth of field. If you lower the max size it renders in a decent amount of time.

If you do it in post you can get away with lower rendertime even.

Ok it crashes because the rendering is too heavy (takes too much time to render). What is taking the most time is the Depth of field. If you lower the max size it renders in a decent amount of time. If you do it in post you can get away with lower rendertime even.

Brecht Van Lommel commented

2019-06-06 12:44:37 +02:00

Not a high priority bug anymore as far as I can see, now that the system lockup is fixed and it's a driver timeout type of issue.

Philipp Oeser changed title from ~~Entire Program crashes when Rendering Animation Image Sequence~~ to Eevee crash (caused primarily by very shallow Depth of Field)

2019-09-20 10:27:54 +02:00

Philipp Oeser commented

2019-09-20 10:29:45 +02:00

Added subscribers: @MarcinTwarowski, @lichtwerk, @mano-wii

Philipp Oeser commented

2019-11-20 10:05:10 +01:00

Added subscribers: @JTDM, @MaciejJutrzenka

Clément Foucault was unassigned by Dalai Felinto

2019-12-23 16:34:16 +01:00

Clément Foucault changed title from ~~Eevee crash (caused primarily by very shallow Depth of Field)~~ to EEVEE: Crash if computation is too heavy for the system (TDR issue)

2020-06-23 23:18:30 +02:00

Philipp Oeser removed the

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

EEVEE: Crash if computation is too heavy for the system (TDR issue) #65223