{"id":32306,"date":"2021-04-30T17:14:00","date_gmt":"2021-04-30T21:14:00","guid":{"rendered":"https:\/\/mjtsai.com\/blog\/?p=32306"},"modified":"2021-05-25T15:58:51","modified_gmt":"2021-05-25T19:58:51","slug":"catalina-security-update-2021-002-breaks-opencl","status":"publish","type":"post","link":"https:\/\/mjtsai.com\/blog\/2021\/04\/30\/catalina-security-update-2021-002-breaks-opencl\/","title":{"rendered":"Catalina Security Update 2021-002 Breaks OpenCL"},"content":{"rendered":"

Gus Mueller<\/a> (tweet<\/a>):<\/p>\n

Core Image, another framework by Apple and one that Acorn relies on heavily, uses OpenCL to process images when its renderer is set to “software” mode (the other mode is to use the GPU). Core Image tries to use OpenCL and then fails, so all images come out empty.<\/p>

The quick fix is to tell Core Image not use the software renderer, and then Core Image will move everything to the GPU for processing and use Apple’s Metal framework instead of OpenCL — for most cases. I think there is still hardware out there that can’t use Metal, so it might fall back to OpenCL in that case.<\/p>

[…]<\/p>

Nothing in the release notes for the security update<\/a> mentions OpenCL. I’m baffled and completely in the dark as to what the changes were or why they were done.<\/p><\/blockquote>\n\n

Colin Cornaby<\/a>:<\/p>\n

\n

Also spent the morning diagnosing this. Catalina Macs suddenly stopped completely tests successfully, traced the timing back to the security update.<\/p>\n

In our case, OpenCL breaking also breaks parts of CoreImage.<\/p>\n<\/blockquote>\n\n

Previously:<\/p>\n