Maniphest T67137

Render can not be cancelled and crashes
Confirmed, LowKNOWN ISSUE
Actions

Assigned To
None
Authored By
Félix (Felox)
Jul 17 2019, 6:33 PM
Tags
  • BF Blender
  • EEVEE & Viewport
  • Render Pipeline
  • Render & Cycles
Subscribers
dark999 (dark999)
Félix (Felox)
Jeroen Bakker (jbakker)
Richard Antalik (ISS)
Sebastian Parborg (zeddb)

Description

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

Hello,

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 hangs / crashes.

I launched it using the GPU debug tool

I'm assuming it comes from the hardware.

Thanks in advance.

eevee_logs.txt1 MBDownload

blender2.8.blend1 MBDownload

Exact steps for others to reproduce the error

  • Open the file
  • Render image F12
  • Progress will hang at 0% for too long time
  • Cancel rendering

Render job is not cancelled immediately / Blender crashes with low VRAM

Event Timeline

Félix (Felox) created this task.Jul 17 2019, 6:33 PM
dark999 (dark999) added a subscriber: dark999 (dark999).Jul 17 2019, 7:35 PM

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

system-info_a36a44bb811d.txt31 KBDownload

Jeroen Bakker (jbakker) added a subscriber: Jeroen Bakker (jbakker).Jul 18 2019, 10:17 AM

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.

Félix (Felox) added a comment.Jul 18 2019, 3:58 PM

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.

Sebastian Parborg (zeddb) added a subscriber: Sebastian Parborg (zeddb).Jul 18 2019, 5:52 PM

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

Philipp Oeser (lichtwerk) lowered the priority of this task from 90 to 80.Sep 3 2019, 3:24 PM
Philipp Oeser (lichtwerk) added a project: EEVEE & Viewport.
Richard Antalik (ISS) renamed this task from EEVEE could not render to Render can not be cancelled and crashes.Jan 3 2020, 5:27 AM
Richard Antalik (ISS) updated the task description.
Richard Antalik (ISS) changed the task status from Needs Information from Developers to Confirmed.Jan 3 2020, 5:29 AM
Richard Antalik (ISS) added a project: Render Pipeline.
Richard Antalik (ISS) added a subscriber: Richard Antalik (ISS).

@Félix (Felox) after reducing metaball resolution to 0.05 and decreasing render samples to 128 I wasn't able to reproduce issues you described. These would be best to report separately, But first please re-test your case with latest builds

In T67137#726405, @Sebastian Parborg (zeddb) wrote:

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

Yes, metaball polygonization process is still running after you cancel render.
Since this is subject of the report, I am confirming.

Bastien Montagne (mont29) changed the subtype of this task from "Report" to "Bug".Jan 20 2020, 8:29 PM
Jeroen Bakker (jbakker) triaged this task as Low priority.Jan 21 2020, 11:40 AM
Jeroen Bakker (jbakker) changed the subtype of this task from "Bug" to "Known Issue".

Metaballs has no active maintainer/developer. Will mark this issue as Known Issue as we don't know if it will be picked up in the next 6 months.

Brecht Van Lommel (brecht) added a project: Render & Cycles.Jun 18 2020, 7:03 PM
Clément Foucault (fclem) moved this task from Backlog to Known Issues on the EEVEE & Viewport board.Jun 23 2020, 11:56 PM