Page MenuHome

gpu module in CustomRenderEngine causes segfault
Confirmed, LowPublicKNOWN ISSUE

Description

System Information
Operating system: Linux-5.4.2-arch1-1-x86_64-with-glibc2.29 64 Bits
Graphics card: Mesa DRI Intel(R) HD Graphics 620 (Kaby Lake GT2) Intel Open Source Technology Center 4.5 (Core Profile) Mesa 19.2.7

Blender Version
Broken: version: 2.81 (sub 16), branch: makepkg, commit date: 2019-12-04 11:32, hash: rBf1aa4d18d49d
Worked: (optional)

Short description of error
Using gpu module in CustomRenderEngine render function causes segfault

Exact steps for others to reproduce the error

  • Open attached blendfile
  • Run the python script from text editor
  • change render engine to custom
  • hit f12 (blender crashes)

Is the GPU module not suited for use in CustomRenderEngine ?
Also testet drawing a gpu.types.GPUBatch to a framebuffer object without doing matrix.push_pop(), it also caused a segfault. The matrix thing is just the simplest case to reproduce.

Related Objects

Event Timeline

Germano Cavalcante (mano-wii) lowered the priority of this task from 90 to Low.Dec 16 2019, 8:42 PM

This is a known limitation.
Rendering with F12 is done on another thread, and other threads do not have GLcontext (used by the GPU module).
We could enable a GLcontext for this case (as it is done in eevee), but this could add overhead to other external render engines, and it wouldn't solve all the problems.
A new solution to this will be planned, but it is not the priority for now. (probably during the T68977).

I will confirm the bug to keep a track.

Jeroen Bakker (jbakker) changed the subtype of this task from "Report" to "Known Issue".Tue, Jan 7, 12:36 PM