Unable to finish benchmarks with Victor #83431

New Issue

Xerz · 2020-12-05T13:25:49+01:00

Xerz commented

2020-12-05 13:25:49 +01:00

System Information
Operating system: Windows 10 20H2 19042.630
Graphics card: AMD Radeon RX 6800 (OpenCL)

Blender Version
Broken: Blender Benchmark Launcher 2.0.4, Blender 2.90

Short description of error
When benchmarking with the Victor scene, it finishes reporting the error "Did not receive Benchmark JSON Data". This happens regardless of which renders are chosen, as long as Victor is part of the batch job.

Error ID: 9cda84801e60447f9fb2abbc41b2e2ab

**System Information** Operating system: Windows 10 20H2 19042.630 Graphics card: AMD Radeon RX 6800 (OpenCL) **Blender Version** Broken: Blender Benchmark Launcher 2.0.4, Blender 2.90 **Short description of error** When benchmarking with the Victor scene, it finishes reporting the error "Did not receive Benchmark JSON Data". This happens regardless of which renders are chosen, as long as Victor is part of the batch job. Error ID: 9cda84801e60447f9fb2abbc41b2e2ab

Xerz commented

2020-12-05 13:25:49 +01:00

Added subscriber: @espectalll

Xerz commented

2020-12-05 13:28:43 +01:00

I apologize beforehand if I did any mistakes reporting the bug, as this is my first time opening a ticket on Blender.

Xerz commented

2020-12-05 20:04:43 +01:00

After searching up similar issues from other people, I learned to use the Benchmark CLI tool, so now I have a detailed log from the moment in which rendering consistently fails:

Here's what I consider is the relevant part:

BLENDER: I1205 19:31:00.526888 15012 light.cpp:715] Background MIS build time 0.0022489
BLENDER: I1205 19:31:00.526888 15012 device_opencl_impl.cpp:1163] Global memory allocate: __light_background_marginal_cdf, 8,200 bytes. (8.01K)
BLENDER: I1205 19:31:00.526888 15012 device_opencl_impl.cpp:1163] Global memory allocate: __light_background_conditional_cdf, 16,785,408 bytes. (16.01M)
BLENDER: Fra:2472 Mem:10939.31M (Peak 11133.94M) | Time:01:02.06 | Mem:4575.27M, Peak:4639.27M | Scene, RenderLayer | Updating Lights | Importance map | Compiling render kernels
BLENDER: Fra:2472 Mem:10939.31M (Peak 11133.94M) | Time:01:02.06 | Mem:4575.27M, Peak:4639.27M | Scene, RenderLayer | Updating Lights | Importance map
BLENDER: Fra:2472 Mem:10962.24M (Peak 11133.94M) | Time:01:02.06 | Mem:4575.27M, Peak:4639.27M | Scene, RenderLayer | OpenCL error: CL_INVALID_VALUE in clEnqueueWriteBuffer(device->cqCommandQueue, CL_MEM_PTR(new_buffer->device_pointer), CL_FALSE, offset, allocation->mem->memory_size(), allocation->mem->host_pointer, 0, NULL, NULL) (C:\b\buildbot-worker-windows\windows_290\blender.git\intern\cycles\device\opencl\memory_manager.cpp:99)
BLENDER: Error: OpenCL error: CL_INVALID_VALUE in clEnqueueWriteBuffer(device->cqCommandQueue, CL_MEM_PTR(new_buffer->device_pointer), CL_FALSE, offset, allocation->mem->memory_size(), allocation->mem->host_pointer, 0, NULL, NULL) (C:\b\buildbot-worker-windows\windows_290\blender.git\intern\cycles\device\opencl\memory_manager.cpp:99)
BLENDER: I1205 19:31:00.531891 14996 blender_session.cpp:586] Total render time: 55.4946
BLENDER: I1205 19:31:00.531891 14996 blender_session.cpp:587] Render time (without synchronization): -1.28304

I found someone who seems to have the same issue at blender/blender#80454, and indeed, 2.83.0 works. Can't verify 2.83.2 or 2.83.3 from the benchmark tool though, since it does not accept those versions.

After searching up similar issues from other people, I learned to use the Benchmark CLI tool, so now I have a detailed log from the moment in which rendering consistently fails: Here's what I consider is the relevant part: ``` BLENDER: I1205 19:31:00.526888 15012 light.cpp:715] Background MIS build time 0.0022489 BLENDER: I1205 19:31:00.526888 15012 device_opencl_impl.cpp:1163] Global memory allocate: __light_background_marginal_cdf, 8,200 bytes. (8.01K) BLENDER: I1205 19:31:00.526888 15012 device_opencl_impl.cpp:1163] Global memory allocate: __light_background_conditional_cdf, 16,785,408 bytes. (16.01M) BLENDER: Fra:2472 Mem:10939.31M (Peak 11133.94M) | Time:01:02.06 | Mem:4575.27M, Peak:4639.27M | Scene, RenderLayer | Updating Lights | Importance map | Compiling render kernels BLENDER: Fra:2472 Mem:10939.31M (Peak 11133.94M) | Time:01:02.06 | Mem:4575.27M, Peak:4639.27M | Scene, RenderLayer | Updating Lights | Importance map BLENDER: Fra:2472 Mem:10962.24M (Peak 11133.94M) | Time:01:02.06 | Mem:4575.27M, Peak:4639.27M | Scene, RenderLayer | OpenCL error: CL_INVALID_VALUE in clEnqueueWriteBuffer(device->cqCommandQueue, CL_MEM_PTR(new_buffer->device_pointer), CL_FALSE, offset, allocation->mem->memory_size(), allocation->mem->host_pointer, 0, NULL, NULL) (C:\b\buildbot-worker-windows\windows_290\blender.git\intern\cycles\device\opencl\memory_manager.cpp:99) BLENDER: Error: OpenCL error: CL_INVALID_VALUE in clEnqueueWriteBuffer(device->cqCommandQueue, CL_MEM_PTR(new_buffer->device_pointer), CL_FALSE, offset, allocation->mem->memory_size(), allocation->mem->host_pointer, 0, NULL, NULL) (C:\b\buildbot-worker-windows\windows_290\blender.git\intern\cycles\device\opencl\memory_manager.cpp:99) BLENDER: I1205 19:31:00.531891 14996 blender_session.cpp:586] Total render time: 55.4946 BLENDER: I1205 19:31:00.531891 14996 blender_session.cpp:587] Render time (without synchronization): -1.28304 ``` I found someone who seems to have the same issue at blender/blender#80454, and indeed, 2.83.0 works. Can't verify 2.83.2 or 2.83.3 from the benchmark tool though, since it does not accept those versions.

Xerz commented

2020-12-05 20:48:02 +01:00

Made some further testing by downloading multiple versions of Blender manually, and I found 2.90.1 and 2.91.0 no longer have the issue! The solution would thus be as simple as updating the Blender Benchmark Launcher with a 2.91 option, and perhaps blacklist the Victor scene with Blender 2.90 when rendering with the GPU.

Robert Guetzkow commented

2020-12-12 10:29:19 +01:00

Added subscriber: @rjg

Robert Guetzkow commented

2020-12-12 10:29:19 +01:00

If 2.90.1 and later works, then the issue has most likely been solved within the corrective release of 2.90.1. This would be easier to check with a full debug log and crash report.

Could you please download the [Cosmos Laundromat demo file ]] and the portable (*.zip) version of [ https:*download.blender.org/release/Blender2.90/ | Blender 2.90.0 . Extract the .zip and the double click on the on the blender_debug_gpu.cmd. This will start Blender in debug mode and create log files. Try to make Blender crash again. Once it crashes the Windows Explorer should open and show you up to two files, a debug log and the system information. Add them to your bug report by clicking on the upload button as shown in the screenshot below or via drag and drop. Please also upload the crash log located in C:\Users\[your username]\AppData\Local\Temp\[project name].crash.txt (or simply type %TEMP% into the path bar of the Windows Explorer).

You can also try if you can get later versions to crash with the scene.

If 2.90.1 and later works, then the issue has most likely been solved within the corrective release of 2.90.1. This would be easier to check with a full debug log and crash report. Could you please download the [Cosmos Laundromat demo file ]] and the portable (*.zip) version of [[ https:*download.blender.org/release/Blender2.90/ | Blender 2.90.0 ](https:*www.blender.org/download/demo-files/). Extract the .zip and the double click on the on the `blender_debug_gpu.cmd`. This will start Blender in debug mode and create log files. Try to make Blender crash again. Once it crashes the Windows Explorer should open and show you up to two files, a debug log and the system information. Add them to your bug report by clicking on the upload button as shown in the screenshot below or via drag and drop. Please also upload the crash log located in `C:\Users\[your username]\AppData\Local\Temp\[project name].crash.txt` (or simply type `%TEMP%` into the path bar of the Windows Explorer). ![2019_12_04_upload_icon_developer_blender_org.png](https://archive.blender.org/developer/F8190038/2019_12_04_upload_icon_developer_blender_org.png) You can also try if you can get later versions to crash with the scene.

Robert Guetzkow commented

2020-12-12 10:29:26 +01:00

Changed status from 'Needs Triage' to: 'Needs User Info'

Xerz commented

2020-12-13 23:31:30 +01:00

Blender does not crash per se, it's Cycles that fails to render the scene and aborts the process.

Here are the log files, if you check at the end of blender_debug_output.txt you'll see the same CL_INVALID_VALUE error message:
blender_system_info.txt
blender_debug_output.txt
Because Blender itself doesn't crash, there is no .crash.txt file.

Blender does not crash per se, it's Cycles that fails to render the scene and aborts the process. Here are the log files, if you check at the end of `blender_debug_output.txt` you'll see the same `CL_INVALID_VALUE` error message: [blender_system_info.txt](https://archive.blender.org/developer/F9507234/blender_system_info.txt) [blender_debug_output.txt](https://archive.blender.org/developer/F9507235/blender_debug_output.txt) Because Blender itself doesn't crash, there is no `.crash.txt` file.

Robert Guetzkow commented

2021-02-27 18:57:24 +01:00

Changed status from 'Needs User Info' to: 'Needs Triage'

Björn Martin commented

2021-12-20 23:16:00 +01:00

Added subscriber: @Boris59

Björn Martin commented

2021-12-20 23:16:00 +01:00

Changed status from 'Needs Triage' to: 'Resolved'

Björn Martin closed this issue

2021-12-20 23:16:00 +01:00

Björn Martin self-assigned this 2021-12-20 23:16:00 +01:00

Björn Martin commented

2021-12-20 23:16:00 +01:00

I just benchmarked with an AMD Radeon RX 6900 XT using Benchmark Launcher 2.0.4 which offers Blender 2.93.1 by now, and the Victor benchmark works now.

Since the lack of a supported version as part of Benchmark Launcher 2.0.4 was the only issue remaining, I marked this as resolved.

I just benchmarked with an **AMD Radeon RX 6900 XT** using Benchmark Launcher 2.0.4 which offers Blender **2.93.1** by now, and the **Victor** benchmark works now. Since the lack of a supported version as part of Benchmark Launcher 2.0.4 was the only issue remaining, I marked this as resolved.

This repo is archived. You cannot comment on issues.