Crash with OpenCL rendering (AMD APU) #45056
Labels
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
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#45056
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
System Information
windows 8.1
AMD A4-5000 APU with radeon(TM) HD Grafics 1.50 GHz
8gb ram
64 bit operating system, x64-based processor
Blender Version
2.75 (rc)
Short description of error
when i try to render using my GPU it says loading render kernal(may take a few minutes the first time). after a minute the program just closes.
Exact steps for others to reproduce the error
does not have steps i just turned on gpu compute and it does this with all files including startup file.
Changed status to: 'Open'
Added subscriber: @jhonwallace
Added subscriber: @mont29
I’m not sure that kind of low-end 'GPU' can handle at all such a big thing as Cycles kernel (be it split), Sergey?
@jhonwallace can you please run Blender from a console, and report here messages during that loading of render kernel, if any?
Added subscriber: @ThomasDinges
Please make sure that your GPU drivers are up to date.
I had just updated the drivers and that did not seek to solve it.
I watched the system console during the render and it says (not including the four startup lines).
Device init success
Compiling OpenCL kernal ...
Build flags:
And that's it those show up at start of render and thats all that is there when the program closes.
2.75 rcto Crash with OpenCL rendering (AMD APU)Seems your configuration is not recognized as officially supported for split kernel and hence megakernel is used which indeed not really stable.
You can do the following:
If that doesn't help, run blender with --debug-cycles command line argument (from the same terminal). Also having system-info.txt attached here will be handy.
Are you referring to blenders terminal or PC terminal. I'm not sure how I would start blender from the blender terminal.
There's no terminal in blender, blender only has python console ;)
I'm talking about terminal emulator from your operation system, aka cmd.exe or command line tool or whatever it's called in modern windows :)
Silly me. I got you now. I have never been in debug mode and it seems that running it through terminal didn't fix it.
info.txt
this is what i saw in blenders System Console before it closed. i did it through the terminal like you said.
Weird. Can you run
blender.exe --debug-cycles
from the same terminal (dont' forget to set CYCLES_OPENCL_SPLIT_KERNEL_TEST :). THat would give a bit more clues about what's happening in Cycles side.info.txt
i hope that helps. if you need more info let me know.
It seems crash is caused by opencl compiler itself, which is a part of AMD driver. A10 APU seems to work with some latest changes, but other hardware might still need some tweaks.
For now we're only officially supporting AMD GPUs which are GCN and newer. Supporting APU i'd consider a TODO, because it also needs work from AMD about function inline policy.
Tricks like doing feature-selective compilation for shader and baking kernels might help here to make kernel compilable with simplier scenes. It was on own TODO but now i'm mentioned it in there http://wiki.blender.org/index.php/Dev:2.6/Source/Render/Cycles/ToDo#Performance
So thanks for the report, but archiving it for until either we've got developer who can reproduce the issue and try finding a workaround or for until AMD fixes compiler.
Changed status from 'Open' to: 'Archived'
thank you for trying. I hope to use gpu in the future but im in no rush. :) i render using two cpus so im not in in serious need for gpu computing i just thought id give it a shot. both computers i use are very different but niether can use gpu but they are doing just fine for what i need. i love the Blender program and cant wait for what comes in the next updates!!!