Mar 3 2018
Sure, here is a blend.
(texture is bundled, but in just in case...)
I can reproduce it with an base material and an Image Texture like Color Grid attached to it on win 7 AMD R7 360 in Texture mode. Tested with build fee4b64, 2.79a RC.
Running with debug-gpu gives the following error:
I can't reproduce this so far. Can you attach a .blend and image texture, to be sure there isn't anything different about what we are testing with?
Feb 19 2018
I believe that I might also be suffering from this bug.
Feb 9 2018
It still doesn't seem to work with the edge split modifier. Compare renderings in Cycles vs. Eevee with smooth faces, sharp edges + edge split modifier (using blender2.8 / be4ebb7fa6c).
Feb 1 2018
no GPU rendering for me then,
Jan 31 2018
After looking through now with proper time, seems indeed some High Sierra issue.
From the description, this must be a bug in the Apple OpenCL driver. We've seen this before where if it's given a complex OpenCL kernel, it can hang for a longe time and eventually crash or return an error.
So I'll open this again, yet I can't repro.
Factory startup is just that, it removes all settings to default, and removes GPU compute selection from settings.
Check if this happens with 2.79a-rc:
Blender 2.79a rc macOS
As it seems that it's not blender bug, marking this as resolved. Feel free to comment, I'll try to help.
Start with --factory-startup, then do some settings you usually have, and save it as new startup.blend
... can you give me an idea what to try then? I'm not a coding guru. (Unless chaos is worshipped, I that case I may stand a fair chance)
It can be also your startup .blend
Ah, it is not an add on problem,
Don't know why, but I recompiled and it works now.
Jan 30 2018
Console gives this output though, (see attachement)
When switching to factory settings, enabling Cycles and then switch to GPU and start a render, it actually works!
If you start with --factory-startup, does the kernel compiling hang?
Here's the terminal output:
I would like to see the terminal console, it seems to hang when trying to build OpenCL kernels.
No, not really,
but here's a screenshot, so you can look for yourself, perhaps spot something I've missed...
Does --debug-gpu option give anything to the console before freeze?
Jan 26 2018
This must be some issue with opening new windows when using multiple GPUs. I don't have a similar system setup to test this though, hopefully another developer can reproduce it..
Jan 24 2018
Jan 23 2018
Jan 19 2018
Jan 13 2018
Problem has not been fixed for me. It still flickers and stops responding everytime i click something and crashes whenever i minimize. I'm using latest 2.79 and a Radeon Vega 64.
Jan 12 2018
Since last asking for information it has been 7 or more days, due to the policy of our bug tracker we will have to archive the report until the requested information is given.
Jan 11 2018
Jan 5 2018
@Edwin Andres Martinez Suarez: since you were mentioning you upgraded linux (and thus propably nouveau as well): could you tell us if this problem still persists?
since I guess both of the above didnt solve the problem, but the information was given: reopening
Jan 3 2018
Thank you for the report. Currently we are aware of many issues in 2.8 and actively working to fix them. But since replying to reports takes time, we have decided to limit bug reports to module team members.
Dec 20 2017
Already in master
Dec 16 2017
I'm getting the same error on a AMD 5800K APU, which has the Radeon HD 7660D GPU, on startup in 2.8. The default cube displays, but its shader is just a bunch of random noise. I should mention that this only occurs with Eevee, and not any of the other render engines.
Dec 15 2017
Getting the same issue here on Linux with an AMD 5800K APU. Apparently, gpu_basic_shader is returning a null pointer which gets passed to GPU_shader_get_uniform, which then tries to point/access elements in that structure, resulting in a segfault.
Dec 13 2017
Dec 8 2017
More than a week passed without a reply.
Dec 7 2017
I just tested latest buildbot 2.8 with new intel hd 4600 drivers installed, and... it did not work. Here is error from console:
Dec 5 2017
Yep that's something on my TODO list for sure.
Thanks for the report, but this is a known limitation since initial Clipping implementation in Cycles: for GLSL e really need to use OpenGL clipping, which is fast but which would requite some internal changes in how we work with OpenGL textures. Currently, we only use one OpenGL texture per image, which will cause unpredictable results if the same image is used with different clipping/extension methods.