OpenCL - CPU + GPU + GPU = Crash #44831

New Issue

Grzegorz Wereszko · 2015-05-24T22:16:47+02:00

Grzegorz Wereszko commented

2015-05-24 22:16:47 +02:00

System Information
Windows 7 64bit
Nvidia GTX 680
AMD R9 290X
AMD FX-8350

Blender Version
Broken:

Build : blender-2.75-testbuild1-windows64

 - OpenCL on CPU - Crash
 - OpenCL on CPU + GTX 680 + R9 290X - Crash

Worked:
- OpenCL on GTX 680 - worked
- OpenCL on R9-290x - worked

Short description of error
Application crashes when rendering

Exact steps for others to reproduce the error
With attached file. When changing rendering from CPU to GPU and in user preference changing the OpenCL device to FX8350 CPU, it crashes. If selected in user preference all devices (CPU + Nvidia GPU + AMD GPU) it also crashes.

Lack of option to select Nvidia GPU + AMD GPU OpenCL devices to test if the error is simply caused due to the OpenCL CPU code.

INcluded file does not have every element linked (as the HDR - hence purple hue - so that can be ignored?)

table2.blend

**System Information** Windows 7 64bit Nvidia GTX 680 AMD R9 290X AMD FX-8350 **Blender Version** Broken: ``` Build : blender-2.75-testbuild1-windows64 ``` - OpenCL on CPU - Crash - OpenCL on CPU + GTX 680 + R9 290X - Crash Worked: - OpenCL on GTX 680 - worked - OpenCL on R9-290x - worked **Short description of error** Application crashes when rendering **Exact steps for others to reproduce the error** With attached file. When changing rendering from CPU to GPU and in user preference changing the OpenCL device to FX8350 CPU, it crashes. If selected in user preference all devices (CPU + Nvidia GPU + AMD GPU) it also crashes. Lack of option to select Nvidia GPU + AMD GPU OpenCL devices to test if the error is simply caused due to the OpenCL CPU code. INcluded file does not have every element linked (as the HDR - hence purple hue - so that can be ignored?) [table2.blend](https://archive.blender.org/developer/F179693/table2.blend)

Grzegorz Wereszko commented

2015-05-24 22:16:47 +02:00

Changed status to: 'Open'

Grzegorz Wereszko commented

2015-05-24 22:16:47 +02:00

Added subscriber: @Prodeous

Thomas Dinges commented

2015-05-24 23:59:47 +02:00

Added subscribers: @Sergey, @ThomasDinges

Thomas Dinges commented

2015-05-24 23:59:47 +02:00

I can confirm crashes here with Intel i7 + Nvidia Geforce 540M on Windows 7 x64.
It's the Intel device that crashes here, the Nvidia one alone works fine.

@Sergey: We might want to limit multi device somehow? Vanilla Master (without environment flags) will use both split and mega kernel and different feature sets in such a setup. Ideally this should only result in render differences per tile, but there might be something else that goes wrong.

I can confirm crashes here with Intel i7 + Nvidia Geforce 540M on Windows 7 x64. It's the Intel device that crashes here, the Nvidia one alone works fine. @Sergey: We might want to limit multi device somehow? Vanilla Master (without environment flags) will use both split and mega kernel *and* different feature sets in such a setup. Ideally this should only result in render differences per tile, but there might be something else that goes wrong.

Sergey Sharybin commented

2015-05-25 11:31:14 +02:00

@ThomasDinges, it is handy to keep CPU OpenCL working for the development purposes. the option is not whitelisted by default as far as i concerned, so any use of it is kinda "on own risk" and "for investigation purposes only".

I can not reproduce crash on my laptop with windows 7 and i5 CPU, regardless if it's just CPU or CPU+GPU (GPU is gt520m).

What's the version of intel opencl sdk you're using?

@ThomasDinges, it is handy to keep CPU OpenCL working for the development purposes. the option is not whitelisted by default as far as i concerned, so any use of it is kinda "on own risk" and "for investigation purposes only". I can not reproduce crash on my laptop with windows 7 and i5 CPU, regardless if it's just CPU or CPU+GPU (GPU is gt520m). What's the version of intel opencl sdk you're using?

Thomas Dinges commented

2015-05-25 11:39:34 +02:00

I got it from here: https://software.intel.com/en-us/articles/opencl-drivers

"OpenCL™ Runtime 15.1 for Intel® Core™ and Intel® Xeon® Processors for Windows* OS (64-bit & 32-bit)"

I got it from here: https://software.intel.com/en-us/articles/opencl-drivers "OpenCL™ Runtime 15.1 for Intel® Core™ and Intel® Xeon® Processors for Windows* OS (64-bit & 32-bit)"

Sergey Sharybin commented

2015-05-25 11:47:57 +02:00

@ThomasDinges, excellent. So did i =/ Will give it another attempt to reproduce the issue again later.

One more question tho: are you using own builds or builds from buildbot?

@ThomasDinges, excellent. So did i =/ Will give it another attempt to reproduce the issue again later. One more question tho: are you using own builds or builds from buildbot?

Thomas Dinges commented

2015-05-25 12:35:16 +02:00

Self build (Scons), but I double checked with "blender-2.74-7fd93dc-win64" from Buildbot just now and it crashes as well, default cube scene and the blend from this report.

Sergey Sharybin commented

2015-05-25 15:57:19 +02:00

Assigning BF Blender: Next project sine it's nice to have this addressed prior to RC.

Grzegorz Wereszko commented

2015-05-25 18:02:54 +02:00

I would recommend that for current release the CPU option is disabled till solution is in place. Most people do not know the option is "on own risk" and "for investigation purposes only". If we see this option we would like it to not crash the applicaiton.

additionally i'm curious why I can't select just both of the GPU's (680+r9290) excluding the CPU option. I want to test if the two GPU's can cooperate in one render.

I would recommend that for current release the CPU option is disabled till solution is in place. Most people do not know the option is "on own risk" and "for investigation purposes only". If we see this option we would like it to not crash the applicaiton. additionally i'm curious why I can't select just both of the GPU's (680+r9290) excluding the CPU option. I want to test if the two GPU's can cooperate in one render.

Sergey Sharybin commented

2015-05-25 19:29:44 +02:00

If you can see non-AMD GPU in the OpenCL list without setting any of the environment variables then there's bug in the device enumeration.

If you're setting environment variable then you're expected to see all the devices. By setting the variable you're already agreeing that there might be some issues. Forcing CPU from being always disabled is the wrong solution because while it crashes for someones for others it works just fine.

If you can see non-AMD GPU in the OpenCL list without setting any of the environment variables then there's bug in the device enumeration. If you're setting environment variable then you're expected to see all the devices. By setting the variable you're already agreeing that there might be some issues. Forcing CPU from being always disabled is the wrong solution because while it crashes for someones for others it works just fine.

Martijn Berger commented

2015-05-26 11:15:14 +02:00

Added subscriber: @MartijnBerger

Martijn Berger commented

2015-05-26 11:15:14 +02:00

additionally i'm curious why I can't select just both of the GPU's (680+r9290) excluding the CPU option. I want to test if the two GPU's can cooperate in one render.

Well our multi device does not show all combinations of devices possible. The combo box selector thingy would become very very very long in some situations and this is technically not hard to solve but it involves touching the UI.

``` additionally i'm curious why I can't select just both of the GPU's (680+r9290) excluding the CPU option. I want to test if the two GPU's can cooperate in one render. ``` Well our multi device does not show all combinations of devices possible. The combo box selector thingy would become very very very long in some situations and this is technically not hard to solve but it involves touching the UI.

blender-admin commented

2015-05-26 18:29:21 +02:00

This issue was referenced by cf19012fb0

This issue was referenced by cf19012fb0f61f4b1af6c05d3fbce9649a56147c

Sergey Sharybin commented

2015-05-26 18:29:33 +02:00

Changed status from 'Open' to: 'Resolved'

Sergey Sharybin closed this issue

2015-05-26 18:29:33 +02:00

blender-admin commented

2015-06-01 16:52:44 +02:00

This issue was referenced by blender/cycles@6f24f462fa

This issue was referenced by blender/cycles@6f24f462fa2c282431525d524b3652b8b44db50f

Sign in to join this conversation.

No Label

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

OpenCL - CPU + GPU + GPU = Crash #44831