17.1b7+ Crashing on Mac M1 - OpenCL

When trying 17.1b7 on an M1 Mac using OpenCL, Resolve is crashing...

Code: Select all

==========[CRASH DUMP]==========
#TIME Thu Jan 21 19:05:30 2021 - Uptime 00:01:36 (hh:mm:ss)
#PROGRAM_NAME DaVinci Resolve Studio v17.1.0b.0013 (macOS/Clang arm64)
#BMD_ARCHITECTURE arm64
#BMD_BUILD_UUID 9ef5a4c6-8c38-4db0-9ee8-349231efbdc5
#BMD_GIT_COMMIT 9963cc10e804863fdce4bbd82e21abcf05dd5aa8
#BMD_UTIL_VERSION 17.1.0b.0013
#OS macOS

0   Resolve                             0x0000000102376294 Resolve + 352916
1   Resolve                             0x0000000102375578 Resolve + 349560
2   libsystem_platform.dylib            0x000000019fc1cc44 _sigtramp + 56
3   Resolve                             0x0000000104dd7aa8 _ZN17QtMetaTypePrivate23QMetaTypeFunctionHelperIP9QKeyEventLb1EE9ConstructEPvPKv + 307136
4   Resolve                             0x0000000104c354d8 _ZN7DaVinci9Converter5Video5dpx10INS1_12dpx10conv_LEEE18VectorConvertTo16uEPKciPciii + 223904
5   Resolve                             0x0000000104c34cb8 _ZN7DaVinci9Converter5Video5dpx10INS1_12dpx10conv_LEEE18VectorConvertTo16uEPKciPciii + 221824
6   Resolve                             0x0000000104c3634c _ZN7DaVinci9Converter5Video5dpx10INS1_12dpx10conv_LEEE18VectorConvertTo16uEPKciPciii + 227604
7   Resolve                             0x0000000104aa7410 _ZN33IOMXFDolbyVisionMetadataExtractor11IOMXFReader14s_ReceiveFrameEP18_MXFReaderListeneriPhj + 28740
8   Resolve                             0x0000000104b745e8 _ZN5boost16re_detail_10620012perl_matcherINSt3__111__wrap_iterIPKwEENS2_9allocatorINS_9sub_matchIS6_EEEENS_12regex_traitsIwNS_16cpp_regex_traitsIwEEEEE11unwind_caseEb + 465812
9   Resolve                             0x0000000104cf86c0 _ZN5boost16re_detail_10620012perl_matcherIPKcNSt3__19allocatorINS_9sub_matchIS3_EEEENS_12regex_traitsIcNS_16cpp_regex_traitsIcEEEEE11unwind_caseEb + 107104
10  Resolve                             0x0000000104bb8f70 _ZN5boost16re_detail_10620012perl_matcherINSt3__111__wrap_iterIPKwEENS2_9allocatorINS_9sub_matchIS6_EEEENS_12regex_traitsIwNS_16cpp_regex_traitsIwEEEEE11unwind_caseEb + 746780
11  Resolve                             0x0000000104bbc81c _ZN5boost16re_detail_10620012perl_matcherINSt3__111__wrap_iterIPKwEENS2_9allocatorINS_9sub_matchIS6_EEEENS_12regex_traitsIwNS_16cpp_regex_traitsIwEEEEE11unwind_caseEb + 761288
12  Resolve                             0x0000000104ae7618 _ZN33IOMXFDolbyVisionMetadataExtractor11IOMXFReader14s_ReceiveFrameEP18_MXFReaderListeneriPhj + 291404
13  Resolve                             0x0000000103d2b004 _ZN5boost2io6detail13call_put_lastIcNSt3__111char_traitsIcEEKmEEvRNS3_13basic_ostreamIT_T0_EEPKv + 247600
14  Resolve                             0x0000000104df4c54 _ZN17FontRenderItemVec14CreateInstanceEv + 42232
15  Resolve                             0x0000000104df14f0 _ZN17FontRenderItemVec14CreateInstanceEv + 28052
16  Resolve                             0x0000000104e1e8b8 _ZN5boost6detail8function22void_function_invoker3IPFvibbEvibbE6invokeERNS1_15function_bufferEibb + 41968
17  Resolve                             0x0000000103d224b4 _ZN5boost2io6detail13call_put_lastIcNSt3__111char_traitsIcEEKmEEvRNS3_13basic_ostreamIT_T0_EEPKv + 211936
18  Resolve                             0x00000001024006b8 _ZN14BtSerializable14CreateInstanceEv + 54912
19  libsystem_pthread.dylib             0x000000019fbd506c _pthread_start + 320
20  libsystem_pthread.dylib             0x000000019fbcfda0 thread_start + 8
Signal Number = 11

It happens not long after Resolve is started when trying to add media into project (specifically where there are multiple media files in the Media Storage browser)

17.0 beta7 is not for the M1 !

you must wait BMD has 17.1 beta7 for download in a few days



and your signature is not funny, but prevents people from helping you,
because it does not show what hardware and system is used!




.

Typo on my part. It's 17.1 beta 7 - it's already on the support page

ok, wasn't yesterday

Further info:

It looks like this is happening on 8-bit 4:2:0 encoded media (H264)

10-bit 4:2:2 seems fine

Why not use Metal? The GPU is optimised for that.
I can export H.264 8 bit just fine.

Why not use Metal? The GPU is optimised for that.
I can export H.264 8 bit just fine.

I came across the issue as part of some dev testing, hence why I've reported it. As it stands, OpenCL may be deprecated but it's still not removed.

The problem is observed when trying to import media. It could possibly manifest elsewhere as well, but that's what I've noted.

Sounds like a feature more than a bug. It's for those V-LOG L users that insist on using 8-bit rather than 10-bit and complaining about the resulting banding/etc in their color graded work. Just kidding.

I see two reasons I didn't run into this then, I use the default metal for GPU and I always use 10-bit 4-2-2 All-I for my footage (yeah, you can easily tell I'm a Panasonic user).

As a dev/tester, kudos for catching an issue that many might not encounter so that BMD can correct it. Helps for the OpenCL situations if/when Apple designs an "Apple Silicon Mac Pro" in the future. Suspect however most would still work with the defaults, like myself, and this bug would not have been detected.

Still getting crashes in Beta 8.

This issue doesn't appear to manifest in Beta 6 or earlier.

Also getting crashes in Beta 9.

After some further testing, I've narrowed it down to 4K (UHD) 8-bit 4:2:0 footage.

In my particular case, this was observed with XAVC footage, though other codecs might have the same issues.

Sample file for testing: https://gofile.io/d/py9tga

I can confirm this. Crashing if set to OpenCL, playing without a problem if set to Metal.
Maybe the devs should abandon Open CL for M1?

Please PM if my log is needed too.

[Rohit Gupta]

Please do not use OpenCL on M1. Only use Metal.