Blender 3.0 Crash when Cycles rendering GPU+CPU #91994

New Issue

Vas · 2021-10-06T23:29:06+02:00

Vas commented

2021-10-06 23:29:06 +02:00

System Information
Operating system: Windows-10-10.0.17763-SP0 64 Bits
Graphics card: NVIDIA GeForce GTX 1050 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 472.12

Blender Version
Broken: version: 3.0.0 Alpha, branch: master, commit date: 2021-10-05 22:29, hash: 26dac33ce1
Worked: version: 3.0.0 Alpha, branch: master, commit date: 2021-10-04 20:40, hash: 18959c502d

Short description of error
On this build, using GPU+CPU with Cycles render crashes Blender
Using each one of them separately causes no issues
Video demo below
2021-10-06 22-22-23.mp4

Exact steps for others to reproduce the error
[Please describe the exact steps needed to reproduce the issue]

Default file
go to Edit>Preferences>System and enable both CPU and GPU
Set render engine to Cycles
Set Device to GPU compute
Press F12 to render
Crash

**System Information** Operating system: Windows-10-10.0.17763-SP0 64 Bits Graphics card: NVIDIA GeForce GTX 1050 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 472.12 **Blender Version** Broken: version: 3.0.0 Alpha, branch: master, commit date: 2021-10-05 22:29, hash: `26dac33ce1` Worked: version: 3.0.0 Alpha, branch: master, commit date: 2021-10-04 20:40, hash: `18959c502d` **Short description of error** On this build, using GPU+CPU with Cycles render crashes Blender Using each one of them separately causes no issues Video demo below [2021-10-06 22-22-23.mp4](https://archive.blender.org/developer/F10823459/2021-10-06_22-22-23.mp4) **Exact steps for others to reproduce the error** [Please describe the exact steps needed to reproduce the issue] - Default file - go to Edit>Preferences>System and enable both CPU and GPU - Set render engine to Cycles - Set Device to GPU compute - Press F12 to render - Crash

Vas commented

2021-10-06 23:29:06 +02:00

Added subscriber: @Alumx

Nico Traber commented

2021-10-07 09:37:24 +02:00

Added subscriber: @Nico-Traber

Nico Traber commented

2021-10-07 09:41:40 +02:00

I can confirm this. I have experienced the same thing.

Info Log:

Illegal address in CUDA queue synchronize (film_convert_combined_half_rgba)

I can confirm this. I have experienced the same thing. Info Log: ``` Illegal address in CUDA queue synchronize (film_convert_combined_half_rgba) ```

Sergey Sharybin self-assigned this 2021-10-07 10:16:16 +02:00

Omar Emara commented

2021-10-07 11:23:27 +02:00

Added subscriber: @OmarEmaraDev

Omar Emara commented

2021-10-07 11:23:27 +02:00

@Sergey I think the problem is that window_height is not updated in foreach_sliced_buffer_params which then corresponds to the full height and not the height assigned to each device, so the kernels over-reads due to larger work_size = window_width * window_height in run_film_convert_kernels and possibly other places. So likely caused by D12599.

@Sergey I think the problem is that `window_height` is not updated in `foreach_sliced_buffer_params` which then corresponds to the full height and not the height assigned to each device, so the kernels over-reads due to larger `work_size = window_width * window_height` in `run_film_convert_kernels` and possibly other places. So likely caused by [D12599](https://archive.blender.org/developer/D12599).

Sergey Sharybin commented

2021-10-07 11:26:33 +02:00

Indeed your findings are correct. I am working on a fix already.