It's iMac with 5k monitor. @wuxiaowei (cjxw87) indeed you should check the activity monitor if it's CPU or GPU thingie.

@Arto Kitula (akitula) not sure what is an 5k IMac… is it even supposed to support Blender? :P

Confirmed. Short output from debug, so pasting it here rather than adding file =)

Cannot confirm that here on linux, @Arto Kitula (akitula) maybe you can try it on osx?

This seems to happen once in a while on some systems, but I can't repro. Debug build is next possible thing to get more info:
https://www.dropbox.com/s/hk0xxsloy6xeu7z/blender-2.8-ccc8d2ab427-macOS-10.9.tar.gz?dl=0

I read correctly, understood wrong. I'll build OSD sample app soon and will upload it. =)

@Arto Kitula (akitula) There was a misunderstanding.

For switching Intel vs AMD/Nvidia (on dual GPU systems) you can use gfxCardStatus But as said on irc, we're updating libraries, and that OpenSubdiv problem should be solved.

Please:

• Give us your exact Blender, OS and GPU (including drivers) versions, as requested in the template!
• Ensure both your OS and drivers are fully up-to-date (and use official GPU drivers, not those provided by windows or tablet/laptop maker or open source ones in linux distributions).
• Try to start Blender in factory settings (--factory-startup commandline option) (this will ensure whether this is a userpref or addon issue or not).
• Try to tweak OGL settings in UserPreferences, System tab.
• Try to tweak your GPU driver settings (e.g. try different values between 'performance' and 'quality' if you have such slider, etc.).
• Attach as text file here the report generated by Help -> System Info (do not paste it directly in comment).
• Launch Blender from the command line with --debug-gpu option and attach as text file here any error printed out in the console (do not paste it directly in comment).

More than a week without reply or activity. Due to the policy of the tracker archiving for until required info/data are provided.

I apologize for the mistake, I meant High Sierra, not Yosemite.

Thank you for the work that you are doing, I'm sorry if my previous comment came off as demanding or anything, because it wasn't. I really do appreciate you caring enough to look into, and fix, the bug.

Slightly confusing, Yosemite and 10.13.6 version. Is this really High Sierra 10.13.6?
What computer? iMac 2011 ?

Probably another OSX/OpenGL issue… @Arto Kitula (akitula) maybe you can check on that one? Thanks.

@Vincent Lovett (OathOfPosidon) It's not that it is a lower priority issue it's just that it's hard to debug this particular issue without access to the hardware. But I found someone who has the same issue and live nearby so I will fix this ASAP.

I'm guessing that the Intel thing isn't as high of a priority as others, which is understandable. Just really makes testing Eevee hard when one cant actually use Eevee. As of right now, the main reason I'm not using blender is because Intel users can use the Eevee render engine (nor material preview in both Cycles and Eevee) because it broken for Integrated graphics cards.

@Klaus (Swissflame) yes it's more likely to be an hardware limitation and we should not crash in this situation.

Hello,
with the last version it works.
However, only with HDR's up to 8k, but this is probably due to the hardware, and not to Blender.

macOS 10.13.6
I’m using an iMac with no intel gpu.

@Klaus (Swissflame) Can you still reproduce using the latest version?

From a quick google search it seems to be related to this https://github.com/PixarAnimationStudios/OpenSubdiv/issues/758

More than a week without reply or activity. Due to the policy of the tracker archiving for until required info/data are provided.

Committed from git.

Yes! It's fixed now! Awesome!
Thanks guys.

@Omid (Khanman) Could you give your system info also. (which mac do you have?)

This might be one that was fixed already, @Daniel (danthedeckie) could you try the latest build from buildbot to be sure?

@Arto Kitula (akitula) don’t we have a software-gl script in OSX builds, like we do for linux ones? Anyway, from the log it does looks like a GPU/driver issue, guess you are the best guy to handle that report…

Thanks. @Arto Kitula (akitula) mind checking?

It should be fixed now. Reopen if it is not.

As of right now, Intel Integrated Graphics users are having the black ghosting affect in the Eevee render mode as well. The workbench is working fine, and cycles works fine, but Eevee does not. It has been a bug for some time now, but we havent had a proper means to report it, although it does technically lead to a crash if one tries to edit materials while in the Eevee renderer. A lot of us are eager to use Eevee, as it seems to be an extremely valuable asset, we are not able to though because of this bug. @Clément (clempi)

Most likely OpenGL issue yeah, but unable to repro here. --factory-startup --debug-gpu first to get crashlog. Nothing more to add.

Most likely yet another OpenGL issue… Please:

• Ensure both your OS and drivers are fully up-to-date (and use official GPU drivers, not those provided by windows or tablet/laptop maker or open source ones in linux distributions).
• Try the latest build from our buildbot.
• Try to start Blender in factory settings (--factory-startup commandline option) (this will ensure whether this is a userpref or addon issue or not).
• Try to tweak OGL settings in UserPreferences, System tab.
• Try to tweak your GPU driver settings (e.g. try different values between 'performance' and 'quality' if you have such slider, etc.).
• Launch Blender from the command line with --debug-gpu option and attach as text file here any error printed out in the console (do not paste it directly in comment).
• Try to start in software OpenGL mode (use the blender-softwaregl distributed with official blender, will be slow, but will show whether this is a driver issue or not).

Hello my subject was connected to this one.
WIN 10 processor intel I3 7300 HD graphics 630
last driver win64_24.20.100.6194
blender-2.80-8f01623ef31-win64
yesterday I tried the new version and now I get something normal in solid view
but with EEVEE and cycles the same issue in material view (lookdev) and render view
Open GL is ok in material view
I tried the different setting in viewportsampling to 1 and viewport quality to 0 > no change

I also have the same issue as mentioned above. On an iMac5K with AMD Radeon Pro 580.

Can't find any OpenGl script inside blender app. Nor do I find any information on how to on Google. Here is the text file output after --debug-gpu command.

Version: blender-2.80.0-git20180727.b8ab2a84d32-x86_64
Now can use Eevee render with no crash some times but will always crash if first turn on Display Render Preview (Ctrl Z) and then turn on Screen Space Reflections.

Thanks for the report, we are aware this part of the tool system is incomplete still.

It was actually a Cycles issue due to rBf8b9f4e9bbc1: Cycles: Resumable render implementation for Cycles.