[AMDGPU-pro] Cycles troubles with opencl (CL_OUT_OF_HOST_MEMORY) #50761

New Issue

Pavel · 2017-02-23T08:01:09+01:00

Pavel commented

2017-02-23 08:01:09 +01:00

System Information
OS: Ubuntu 16.04
Kernel: 4.10 x86_64
GPU: Radeon R9 280x
Driver: amdgpu-pro-16.60-379184 x86_64

Blender Version
Broken: blender-2.78-7359cc1060-linux-glibc219-x86_64

Short description of error
Cycles render over gpu return OpenCL error (-6): CL_OUT_OF_HOST_MEMORY

Exact steps for others to reproduce the error

Run blender
Configure it to use opencl
Chenge render engine to cycles
Press F12

Attachments
System-info: system-info.txt
Clinfo: clinfo.txt
Blender --gedug-cycles: blender.txt

**System Information** OS: Ubuntu 16.04 Kernel: 4.10 x86_64 GPU: Radeon R9 280x Driver: amdgpu-pro-16.60-379184 x86_64 **Blender Version** Broken: blender-2.78-7359cc1060-linux-glibc219-x86_64 **Short description of error** Cycles render over gpu return OpenCL error (-6): CL_OUT_OF_HOST_MEMORY **Exact steps for others to reproduce the error** 1) Run blender 2) Configure it to use opencl 3) Chenge render engine to cycles 4) Press F12 **Attachments** System-info: [system-info.txt](https://archive.blender.org/developer/F494322/system-info.txt) Clinfo: [clinfo.txt](https://archive.blender.org/developer/F494323/clinfo.txt) Blender --gedug-cycles: [blender.txt](https://archive.blender.org/developer/F494324/blender.txt)

Pavel commented

2017-02-23 08:01:09 +01:00

Changed status to: 'Open'

Pavel commented

2017-02-23 08:01:09 +01:00

Added subscriber: @Metallikus

Mai Lavelle commented

2017-02-23 11:13:30 +01:00

Added subscriber: @MaiLavelle

Mai Lavelle commented

2017-02-23 11:13:30 +01:00

Changed status from 'Open' to: 'Archived'

Mai Lavelle closed this issue

2017-02-23 11:13:30 +01:00

Mai Lavelle self-assigned this 2017-02-23 11:13:30 +01:00

Mai Lavelle commented

2017-02-23 11:13:30 +01:00

Out of host memory means your computer ran out of memory, theres no bug here.

Pavel commented

2017-02-23 18:20:29 +01:00

Changed status from 'Archived' to: 'Open'

Pavel reopened this issue

2017-02-23 18:20:29 +01:00

Pavel commented

2017-02-23 18:20:29 +01:00

In #50761#418998, @MaiLavelle wrote:
Out of host memory means your computer ran out of memory, theres no bug here.

My card have 3Gb memory.
I get this error when rendering the starting cube.
I have no this error under fglrx.

This is a bug.

> In #50761#418998, @MaiLavelle wrote: > Out of host memory means your computer ran out of memory, theres no bug here. 1) My card have 3Gb memory. 2) I get this error when rendering the starting cube. 3) I have no this error under fglrx. This is a bug.

Lukas Stockner commented

2017-02-24 00:22:51 +01:00

Added subscriber: @LukasStockner

Lukas Stockner commented

2017-02-24 00:22:51 +01:00

Considering that the same build of Blender works on a different driver, I'm pretty sure that AMDGPU is to blame here, not Blender.

Mai Lavelle commented

2017-02-24 01:31:56 +01:00

Changed status from 'Open' to: 'Archived'

Mai Lavelle closed this issue

2017-02-24 01:31:56 +01:00

Mai Lavelle commented

2017-02-24 01:31:56 +01:00

Host memory is system memory, not GPU memory. Either your system ran out of memory or there's a driver bug.

Unless there's some other info you've left out there's nothing we can do, this isn't a bug we can fix in Blender.

Host memory is system memory, not GPU memory. Either your system ran out of memory or there's a driver bug. Unless there's some other info you've left out there's nothing we can do, this isn't a bug we can fix in Blender.

Pavel commented

2017-02-24 08:46:17 +01:00

Changed status from 'Archived' to: 'Open'

Pavel reopened this issue

2017-02-24 08:46:17 +01:00

Pavel commented

2017-02-24 08:46:17 +01:00

In #50761#419112, @LukasStockner wrote:
Considering that the same build of Blender works on a different driver, I'm pretty sure that AMDGPU is to blame here, not Blender.

Under fglrx the holders of such cards get another error: https://developer.blender.org/T49465

In #50761#419123, @MaiLavelle wrote:
Host memory is system memory, not GPU memory.

System has 2Gb free RAM and 4Gb swap memory.
Why the default scene uses more than 6Gb memory to render it over amdgpu-pro OpenCL api? Why cycles render over CPU work fine? It is realy not memory leak in cycles engine?

Top output: top.txt

> In #50761#419112, @LukasStockner wrote: > Considering that the same build of Blender works on a different driver, I'm pretty sure that AMDGPU is to blame here, not Blender. Under fglrx the holders of such cards get another error: https://developer.blender.org/T49465 > In #50761#419123, @MaiLavelle wrote: > Host memory is system memory, not GPU memory. System has 2Gb **free** RAM and 4Gb swap memory. Why the default scene uses more than 6Gb memory to render it over amdgpu-pro OpenCL api? Why cycles render over CPU work fine? It is realy not memory leak in cycles engine? Top output: [top.txt](https://archive.blender.org/developer/F495511/top.txt)

soulfire commented

2017-02-24 10:06:10 +01:00

Added subscriber: @TomG

soulfire commented

2017-02-24 12:03:53 +01:00

This comment was removed by @TomG

*This comment was removed by @TomG*

Mai Lavelle commented

2017-02-24 12:55:24 +01:00

@TomG that is interesting and might point to something we can fix. Its a different issue than the one in this report tho.

Could either of you test the split kernel branch and see if thats any better?

@TomG that is interesting and might point to something we can fix. Its a different issue than the one in this report tho. Could either of you test the split kernel branch and see if thats any better?

Bastien Montagne commented

2017-02-24 13:05:44 +01:00

Added subscribers: @tom-37, @mont29

Bastien Montagne commented

2017-02-24 13:05:44 +01:00

@TomG also, since it’s different issue might be better to report it in different task, better to strictly keep one issue per task. ;)

Bastien Montagne commented

2017-02-24 13:06:23 +01:00

Removed subscriber: @tom-37

soulfire commented

2017-02-24 15:30:37 +01:00

In #50761#419316, @mont29 wrote:
@TomG also, since it’s different issue might be better to report it in different task, better to strictly keep one issue per task. ;)

Ok, I have deleted this comment and open here https://developer.blender.org/T50773

In #50761#419310, @MaiLavelle wrote:
@TomG that is interesting and might point to something we can fix. Its a different issue than the one in this report tho.

Could either of you test the split kernel branch and see if thats any better?

No, I haven't tested split kernel branch. I don't know how.

> In #50761#419316, @mont29 wrote: > @TomG also, since it’s different issue might be better to report it in different task, better to strictly keep one issue per task. ;) Ok, I have deleted this comment and open here https://developer.blender.org/T50773 > In #50761#419310, @MaiLavelle wrote: > @TomG that is interesting and might point to something we can fix. Its a different issue than the one in this report tho. > > Could either of you test the split kernel branch and see if thats any better? No, I haven't tested split kernel branch. I don't know how.

Pavel commented

2017-02-25 17:38:07 +01:00

This comment was removed by @Metallikus

*This comment was removed by @Metallikus*

Pavel commented

2017-02-28 08:55:05 +01:00

Builded from src blender work fine on fglrx: #49465

Nicole Snizek commented

2017-03-08 10:44:51 +01:00

Added subscriber: @Banditka06

Nicole Snizek commented

2017-03-08 10:44:51 +01:00

Same here. Blender 2.77 on Ubuntu 16.10 + AMDGPU-PRO OpenCL driver (hybrid installation with Padoka:ppa Mesa display driver).
After starting rendering on GPU it throws CL_OUT_OF_HOST_MEMORY. Try again and blender crashes.
Host Memory: 16GB
GPU: AMD Radeon HD7870, 2GB

Same here. Blender 2.77 on Ubuntu 16.10 + AMDGPU-PRO OpenCL driver (hybrid installation with Padoka:ppa Mesa display driver). After starting rendering on GPU it throws CL_OUT_OF_HOST_MEMORY. Try again and blender crashes. Host Memory: 16GB GPU: AMD Radeon HD7870, 2GB

Bastien Montagne commented

2017-03-17 13:16:34 +01:00

Added subscriber: @Sergey

Bastien Montagne commented

2017-03-17 13:16:34 +01:00

This could actually be related to #50968? Sounds somewhat similar at least, @Sergey?

This could actually be related to #50968? Sounds *somewhat* similar at least, @Sergey?

Nathan Osman commented

2017-03-24 21:28:03 +01:00

Added subscriber: @nathan-osman

Nathan Osman commented

2017-03-24 21:28:03 +01:00

I'm seeing this as well with a Radeon R9 270X (2 GB vRAM), 16 GB of system RAM, and amdgpu 16.60-379184 on Ubuntu 16.04.

Aaron Carlisle commented

2017-03-28 04:49:01 +02:00

Added subscriber: @Blendify

Aaron Carlisle commented

2017-03-28 04:49:01 +02:00

Please try again with a build from https://builder.blender.org/download/

Martin Capitanio commented

2017-04-02 17:50:21 +02:00

Added subscriber: @capnm

Martin Capitanio commented

2017-04-02 17:50:21 +02:00

I can confirm the same error message with Ubuntu LTS 16.04 + proprietary AMDGPU-PRO Driver 16.6 :

Blender 2.78 (sub 4), Commit date: 2017-04-01 13:29, Hash 3bf0026bec
bpy.context.scene.cycles.device = 'GPU'
F12 -> 
OpenCL error (-6): CL_OUT_OF_HOST_MEMORY

Additionally Blender then later crashes with a segmentation fault:

OpenCL: Error creating command queue
OpenCL error: CL_INVALID_COMMAND_QUEUE in clEnqueueWriteBuffer(cqCommandQueue, CL_MEM_PTR(mem.device_pointer), CL_TRUE, 0, mem.memory_size(), zero, 0, NULL, NULL)
OpenCL: failed to initialize device.
Writing: /tmp/blender.crash.txt

Crash report: blender.crash.txt

I can confirm the same error message with Ubuntu LTS 16.04 + proprietary [AMDGPU-PRO Driver 16.6 ](http://support.amd.com/en-us/kb-articles/Pages/AMDGPU-PRO-Driver-for-Linux-Release-Notes.aspx): ``` Blender 2.78 (sub 4), Commit date: 2017-04-01 13:29, Hash 3bf0026bec bpy.context.scene.cycles.device = 'GPU' F12 -> OpenCL error (-6): CL_OUT_OF_HOST_MEMORY ``` Additionally Blender then later crashes with a segmentation fault: ``` OpenCL: Error creating command queue OpenCL error: CL_INVALID_COMMAND_QUEUE in clEnqueueWriteBuffer(cqCommandQueue, CL_MEM_PTR(mem.device_pointer), CL_TRUE, 0, mem.memory_size(), zero, 0, NULL, NULL) OpenCL: failed to initialize device. Writing: /tmp/blender.crash.txt ``` Crash report: [blender.crash.txt](https://archive.blender.org/developer/F531809/blender.crash.txt)

Mai Lavelle commented

2017-04-21 21:28:02 +02:00

This could be a driver issue with GCN 1 cards as all cards mentioned in this report are that generation. I cant reproduce this with the cards I have available, and if it is a driver bug there's nothing that we can do anyways. There is a new version of the drivers released recently you guys could try, but we may have to drop support for these cards.

Please see here for more info regarding supported cards: https://wiki.blender.org/index.php/Dev:Source/Render/Cycles/OpenCL

This could be a driver issue with GCN 1 cards as all cards mentioned in this report are that generation. I cant reproduce this with the cards I have available, and if it is a driver bug there's nothing that we can do anyways. There is a new version of the drivers released recently you guys could try, but we may have to drop support for these cards. Please see here for more info regarding supported cards: https://wiki.blender.org/index.php/Dev:Source/Render/Cycles/OpenCL

Martin Capitanio commented

2017-04-21 22:22:47 +02:00

Unfortunately you are right, GCN1 arch ;-(
Even after upgrade to the latest AMD driver still the same issue.

OpenGL vendor string: Advanced Micro Devices, Inc.
OpenGL renderer string: AMD Radeon HD 7700 Series
OpenGL core profile version string: 4.5.13474 Core Profile Context 17.10.2
OpenGL core profile shading language version string: 4.50

Unfortunately you are right, GCN1 arch ;-( Even after upgrade to the latest AMD driver still the same issue. ``` OpenGL vendor string: Advanced Micro Devices, Inc. OpenGL renderer string: AMD Radeon HD 7700 Series OpenGL core profile version string: 4.5.13474 Core Profile Context 17.10.2 OpenGL core profile shading language version string: 4.50

Martin Capitanio commented

2017-04-21 23:09:54 +02:00

clinfo 2.1.16.01.12 (mesa), this seems to be a related bug/error:

 Address bits             32, Little-Endian
 Global memory size       624066560 (595.2MiB)
 Global free memory (AMD) <printDeviceInfo:68: get number of CL_DEVICE_GLOBAL_FREE_MEMORY_AMD : error -33>

clinfo.txt

clinfo 2.1.16.01.12 (mesa), this seems to be a related bug/error: ``` Address bits 32, Little-Endian Global memory size 624066560 (595.2MiB) Global free memory (AMD) <printDeviceInfo:68: get number of CL_DEVICE_GLOBAL_FREE_MEMORY_AMD : error -33> ``` [clinfo.txt](https://archive.blender.org/developer/F565623/clinfo.txt)

Fable Fox commented

2017-05-11 05:33:35 +02:00

Added subscriber: @fablefox

Fable Fox commented

2017-05-11 05:33:35 +02:00

Changed status from 'Open' to: 'Archived'

Fable Fox closed this issue

2017-05-11 05:33:35 +02:00

Fable Fox commented

2017-05-11 05:33:35 +02:00

It seems agreed that issue was on GCN1 cards and planned to drop support (?).
Last conversation was on Apr 22.

Archived for now.

1) It seems agreed that issue was on GCN1 cards and planned to drop support (?). 2) Last conversation was on Apr 22. Archived for now.

Muhamad Mahdi Fahrresta Triananda Perkasa commented

2018-04-28 05:29:09 +02:00

Added subscriber: @FaresTP

Yassine Oudjana commented

2020-06-17 10:20:21 +02:00

Added subscriber: @Tooniis

Yassine Oudjana commented

2020-06-17 10:20:21 +02:00

Changed status from 'Archived' to: 'Resolved'

Yassine Oudjana commented

2020-06-17 10:20:21 +02:00

In #50761#429868, @capnm wrote:
clinfo 2.1.16.01.12 (mesa), this seems to be a related bug/error:

Address bits 32, Little-Endian
Global memory size 624066560 (595.2MiB)
Global free memory (AMD) <printDeviceInfo:68: get number of CL_DEVICE_GLOBAL_FREE_MEMORY_AMD : error -33>

clinfo.txt

This is it. Setting some environment variables fixes it: https://community.amd.com/thread/233040

This is a bug in the driver not in Blender.

> In #50761#429868, @capnm wrote: > clinfo 2.1.16.01.12 (mesa), this seems to be a related bug/error: > > Address bits 32, Little-Endian > Global memory size 624066560 (595.2MiB) > Global free memory (AMD) <printDeviceInfo:68: get number of CL_DEVICE_GLOBAL_FREE_MEMORY_AMD : error -33> > > [clinfo.txt](https://archive.blender.org/developer/F565623/clinfo.txt) This is it. Setting some environment variables fixes it: https://community.amd.com/thread/233040 This is a bug in the driver not in Blender.

Yassine Oudjana commented

2020-06-17 10:28:18 +02:00

Changed status from 'Resolved' to: 'Archived'

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

[AMDGPU-pro] Cycles troubles with opencl (CL_OUT_OF_HOST_MEMORY) #50761