LuxCoreRender / LuxCoreRender/BlendLuxCore

[Bug Report] Crash when using GPU as compute device

Open
#1,027 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
877
Forks
108
PR merge metrics
No merged PRs in 30d

Description

Please describe the differences between the expected and observed results:

Expected:

  • OpenCL kernel compiling succeeds within the indicated 15-30 minutes and the scene begins rendering.

Observed:

  • When using Vulkan, RAM usage exploded after a few minutes, then Blender crashed a while later.
  • When using OpenGL, same as with Vulkan only it took less time, and the whole computer froze for a moment.

Steps to reproduce:

  • Start Blender
  • Enable BlendLuxCore add-on
  • Set render engine to LuxCoreRender
  • Set compute device to GPU (CPU doesn't crash)
  • Render image

Please provide a simple test scene as a .blend-file:

  • It happens with the default startup scene (camera, light, default cube)

Screenshots or rendered images:

Image

Error message from Blender console:

  • Vulkan: "'bgl' imported without an OpenGL backend. Please update your add-ons to use the gpu module." (appears when enabling BlendLuxCore in add-on menu)
  • OpenGL: No error message.

Operating System: Windows 11 Pro 24H2
Blender version: 4.5.2
BlendLuxCore version: 2.10.1
Pyluxcore version: 2.10.1
CPU model: i7-13700KF
GPU model: NVIDIA GeForce RTX 4070 Ti (driver 581.08)

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the reported setup: Blender 4.5.2, the BlendLuxCore add-on, LuxCoreRender, and GPU compute using the default startup scene. Reproduce the render with Vulkan and OpenGL while comparing the Blender console output and RAM behavior; CPU rendering is the control case. Done means the reported GPU render no longer causes the observed memory exhaustion, freeze, or crash.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
computer-graphics
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.