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

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

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. =)

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.

Nothing wrong with texture, if Volume is disconnected, the background texture is shown normally.

Confirmed. Unpacking file to disk and using that gives purple. Got crash while testing out, I'll investigate it further.

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

Committed as rB92217a81b59a, we'll work on from that.

We'll split these commits...

Land this, I'll make adjustments if needed.

macOS 10.9 libs here.

• macOS support for crashpad

Committed from git.

+1 for bump up to latest.

You need to use English for bug reporting.

@Campbell Barton (campbellbarton) @Brecht Van Lommel (brecht) how about landing this? Or shall we split blender side from build_environment first and land all changes to blender when svn libs are all updated?

Just went through the whole cmake and seems that there is many errors on newest xcode. Mostly on libraries that need updating anyway.
But for this diff, needs just to take the patch away and remove POSTFIX settings to work on macOS. Working on it, will update this diff later on.

@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?

@Clément Foucault (fclem) tested, works. marking as resolved.

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

This is really hackintosh problem, not blender problem. Because in the end, it's non-supported platform, closing ticket.

Now save it to other location, and upload that file (with images packed) to this ticket, thanks!

@Mike Santiago (suicvne) Could you pack images to the .blend and post it again, just to make sure it doesn't happen on while some image processing. (long shot, but still).

Unable to repro, but as I see it, there is no textures packed into .blend file so might be that we're skipping something.
Crashlog says that Threads 1 to 8 were doing same thing and 1 crashed. (IlmThread)

This is indeed Intel-only thing. I can crash blender on GPU_batch_draw_range_ex when enabling only Intel GPU on my MacBookPro.

Let's keep this incomplete until debug build crashlog.

As said on IRC, build with CMAKE_BUILD_TYPE=Debug so we get possible assert also.

Debug build gives:

Confirmed.

In D3398#79562, @LazyDodo (LazyDodo) wrote:

why not just update D2915?

You could try factory startup to disable all addons, they can mess up with the hotkeys. (start blender from terminal, /Applications/Blender/blender.app/Contents/MacOS/blender--factory-startup
)

On compositing, right? Can't repro, Can you attach pic of your composition node setup?

Purpose of the docker image and the cmake is just to simpify things and isolate most of the dependencies from the system libs. install_deps.sh is not used at all. That makes linux, macOS and windows building more 1:1 =)

But tracker is just for bugs, not for building support. Archiving this for that reason.

What if you move directory /Users/filip/Library/Application Support/Blender/2.79/ away and start blender again, and install the latest cloud addon?

No pressure =)
Let's do also factory startup so your preferences and some addons aren't affecting this:

Oops, that one level up is correct. Could you start the build with all debugging options on. And then just hit import ssl to python console and post the whole debug output.
Marking this as incomplete for now.

That's just as it should. If you go that folder, does it have ssl.py ?

@Philipp Oeser (lichtwerk) yeah, that's ok.

@Sergey Sharybin (sergey) It is possible. I've got script that works, just needs some caring to do neat dmg. I'll push it when ready (next week latest).

@Sergey Sharybin (sergey) Actually just now realized that this happens because of the application translocator, the very reason we give releases on signed DMG.

On my macOS local build, this is working. Might be that buildbot isn't working as it should. svn problem or something like that. @Sergey Sharybin (sergey) ? Or anyone who has access to mac buildbot.

@Trudy Wohlleben (trudyvfx) Yeah that was for you. Run blender with debug options on:
open Terminal and start blender with:

Was the file packed or just like that? Making sure that asset file paths are ok, that rendered out on 2.79b.
Debug output would be nice to trace the error, if it still is there.

What audio interface do you have? Is it next to your GPU? Does this happen on other GPU heavy programs?

This is confirmed. (macOS)

Buildbot Cuda was upgraded to 9.1 then. That's why cubins for sm_2x aren't there anymore.

Oh now I get it. Slowly. =) Fixing.

rBb5b5260464fbb would be ok to add.

Set -W to correct help menu

Comments to D3100 are welcome.

I'll do the changes. It would be good to also fix -W option description "borderless" -> "fullscreen". Do we need more opinions here? =)

This is confirmed, on macOS, fullscreen mode is not enabled on startup even there is -W/--window-borderless option set.
wm_window.c lines around 453. Does @Brecht Van Lommel (brecht), @jens verwiebe (jensverwiebe) or @Martijn Berger (juicyfruit) know/remember history of this?

Unable to repro on macOS

As stated in T52507, libs are EOL. Archiving.

After looking through now with proper time, seems indeed some High Sierra issue.

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

It can be also your startup .blend

If you start with --factory-startup, does the kernel compiling hang?

I would like to see the terminal console, it seems to hang when trying to build OpenCL kernels.

Does --debug-gpu option give anything to the console before freeze?

zip files are possible to extract with macOS without any winzip.

@Philipp Oeser (lichtwerk) , true. Closing.

Unable to reproduce.
Please give more detailed info how this happens, and most simple .blend file where this happens.
GPU/CPU ?

Could you add obj file instead of fbx?

Consulting all knowing internet, I'd suspect this to be driver issue.
Drivers for eGPU are coming this spring. It does already work on some degree with High Sierra but not fully.