Doesnt render on GPU #56244

Closed
opened 2018-08-05 21:30:16 +02:00 by MK · 10 comments

System Information
Windows 10 1803 x64
AMD Radeon RX480
Intel i5-3470
8GB Ram

Blender Version
Broken: 2.79b, blender-2.79-a56ec3dfe3e, blender-2.80-ccf794dfc4c
Worked: none

Short description of error
Doesn't render this one particular project, but renders other projects just fine on GPU
this project is rendering fine on my Radeon Pro WX4100 but crashes on my RX480

Reinstalling blender (with deleting the appdata folder) doesnt help, tried a bunch of drivers: 18.7.1, 18.5.1 and 18.2.1

error messages:
OpenCL error (-4): CL_MEM_OBJECT_ALLOCATION_FAILURE in clEnqueueNDRangeKernel
and others in attached files:
err1.png

err2.png

blender only allocates 3.1GB on my WX4100, the 8GB of my RX4800 should be enough.
the orange brackets in the image editor are moving randomly before i get the error or blender crashes.

**System Information** Windows 10 1803 x64 AMD Radeon RX480 Intel i5-3470 8GB Ram **Blender Version** Broken: 2.79b, blender-2.79-a56ec3dfe3e, blender-2.80-ccf794dfc4c Worked: none **Short description of error** Doesn't render this one particular project, but renders other projects just fine on GPU this project is rendering fine on my Radeon Pro WX4100 but crashes on my RX480 Reinstalling blender (with deleting the appdata folder) doesnt help, tried a bunch of drivers: 18.7.1, 18.5.1 and 18.2.1 error messages: OpenCL error (-4): CL_MEM_OBJECT_ALLOCATION_FAILURE in clEnqueueNDRangeKernel and others in attached files: ![err1.png](https://archive.blender.org/developer/F4132258/err1.png) ![err2.png](https://archive.blender.org/developer/F4132263/err2.png) blender only allocates 3.1GB on my WX4100, the 8GB of my RX4800 should be enough. the orange brackets in the image editor are moving randomly before i get the error or blender crashes.
Author

Added subscriber: @tm9000

Added subscriber: @tm9000

Added subscriber: @s12a

Added subscriber: @s12a

I'm apparently not getting any specific OpenCL error using a debug build of Blender, but I'm getting a program crash on the latest 53c56b2b5f as soon GPU scene rendering with Cycles is initiated by pressing F12, with:

  • AMD Radeon RX480 4GB with Radeon Software 18.7.1
  • Windows 10 Pro x64 (1803)

I've attached a simple file with a cube and the Renderer set to Cycles/GPU Compute. Blender needs to have the OpenCL Compute device in User Preferences set to the GPU as in the example below.

image.png

opencl-gpurendering-cycles.blend
console_output.txt
opencl-gpurendering-cycles.crash.txt

I'm apparently not getting any specific OpenCL error using a debug build of Blender, but I'm getting a program *crash* on the latest 53c56b2b5fd as soon GPU scene rendering with Cycles is initiated by pressing F12, with: - AMD Radeon RX480 4GB with Radeon Software 18.7.1 - Windows 10 Pro x64 (1803) I've attached a simple file with a cube and the Renderer set to Cycles/GPU Compute. Blender needs to have the OpenCL Compute device in User Preferences set to the GPU as in the example below. ![image.png](https://archive.blender.org/developer/F4132777/image.png) [opencl-gpurendering-cycles.blend](https://archive.blender.org/developer/F4132772/opencl-gpurendering-cycles.blend) [console_output.txt](https://archive.blender.org/developer/F4132770/console_output.txt) [opencl-gpurendering-cycles.crash.txt](https://archive.blender.org/developer/F4132769/opencl-gpurendering-cycles.crash.txt)

Added subscribers: @brecht, @mont29

Added subscribers: @brecht, @mont29
Brecht Van Lommel was assigned by Bastien Montagne 2018-08-06 08:57:38 +02:00

@tm9000 Please follow our submission template and guidelines, also read these tips about bug reports, and make a complete, valid bug report, with required info, precise description of the issue (only ONE issue per report!), precise steps to reproduce it, small and simple .blend and/or other files to do so if needed, etc.

@s12a are you sure this is the same issue? @tm9000 says it’s also happening for him in 2.79b official release…

@brecht think you’ll want to check on those?

@tm9000 Please follow our [submission template and guidelines](https:*developer.blender.org/maniphest/task/edit/form/1/), also read [these tips about bug reports](https:*wiki.blender.org/wiki/Process/Bug_Reports), and make a complete, valid bug report, with required info, precise description of the issue (only ONE issue per report!), precise steps to reproduce it, **small and simple** .blend and/or other files to do so if needed, etc. @s12a are you sure this is the same issue? @tm9000 says it’s also happening for him in 2.79b official release… @brecht think you’ll want to check on those?

@mont29
Indeed what I'm seeing appears to be 2.8-specific. Sorry, this is probably a different bug.

@mont29 Indeed what I'm seeing appears to be 2.8-specific. Sorry, this is probably a different bug.
Author

i tried to locate the object that is causing the issue.

i appended it to a new file, rendered it and i got the error. saved it, closed blender and opened the file again and now it renders just fine. this is weird.

edit: if i append the same object to a new project again it works now. but if i try to render the main project it doesn't work.

test.blend system-info.txt

i tried to locate the object that is causing the issue. i appended it to a new file, rendered it and i got the error. saved it, closed blender and opened the file again and now it renders just fine. this is weird. edit: if i append the same object to a new project again it works now. but if i try to render the main project it doesn't work. [test.blend](https://archive.blender.org/developer/F4139558/test.blend) [system-info.txt](https://archive.blender.org/developer/F4139559/system-info.txt)
Author

i just found the problem:
the page file was too small (was set to 256MB), made it bigger and now it renders perfectly.

sorry :/

i just found the problem: the page file was too small (was set to 256MB), made it bigger and now it renders perfectly. sorry :/

Changed status from 'Open' to: 'Archived'

Changed status from 'Open' to: 'Archived'

Thanks for testing, seems it was just running out of memory then.

Thanks for testing, seems it was just running out of memory then.
Sign in to join this conversation.
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
EEVEE & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
4 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#56244
No description provided.