Page MenuHome

EEVEE could not render
Open, Needs Triage by DeveloperPublic


System Information
Operating system: Windows-10-10.0.17763 64 Bits
Graphics card: AMD Radeon R9 200 Series ATI Technologies Inc. 4.5.13570 Core Profile Context 19.7.2 26.20.13001.16003

Blender Version
Broken: version: 2.80 (sub 74), branch: master, commit date: 2019-07-11 13:50, hash: rB06312c6d2db8
Worked: (optional)

Short description of error


I wanted to export some scene using the Eevee render. When I render a frame, the image processing statut is still at 0%. Thus, when I try to cancel it, Blender crashes.

I launched it using the GPU debug tool

I'm assuming it comes from the hardware.

Thanks in advance.

Exact steps for others to reproduce the error

Just open the file, the project is using PBR material addon and an HDR, not linked.



Event Timeline

i can reproduce this bug on OpenSUSE TW linux, AMD FX5380 cpu, 16G ram, GTX 690 Nvidia 430.34

Probably an out of memory issue. The scene uses Meta balls set to 0.005 resolution in a large domain.
To be able to render in EEVEE a draw call must fit in the memory of the GPU. My first guess is that the MetaBall just to large to draw in a single call and therefore crashes.

Okay, I rendered it by downgrading the resolution up to 0.05, some frames appeared to be missing and green (nb the capture 0013-0014). Baking the particle system seems to reduce the numbers of those frame. I also have strange artefact popping in the corner of the render.
I don't know if I should make another post about that.

@Jeroen Bakker (jbakker) I can reproduce blender soft lock on my VEGA card with the opensource drivers.
It starts preparing to render, but never seems to get ready. (VRAM is usage is below 800M).
If I then try to cancel the render, it just sits there and I have to kill blender to close it.

I'm guessing that it has to do with the metaball resolution, but I'm curious if the soft lock is a bug. I would think that it should be possible to cancel out without killing blender.