15.2 & 15.2.1 fail to start on macOS

Get answers to your questions about color grading, editing and finishing with DaVinci Resolve.
  • Author
  • Message
Offline

Fortezza

  • Posts: 4
  • Joined: Thu Dec 06, 2018 8:50 am
  • Real Name: Mario Lombardo

15.2 & 15.2.1 fail to start on macOS

PostThu Dec 06, 2018 8:58 am

I succeed at running 15.1.2 with no issues. However, upon upgrading to DR 15.2 or 15.2.1, it simply does not start on 16GB RAM macOS 10.13.6 (High Sierra). I've never had an issue prior to this since 12.x. Could it be the DB? I've always opted to not upgrade/touch the DB. Where should I look in the log for clues? A cursory search only yielded the mention of refraining from upgrading to 15.2 due to stability issues. Once 15.2.1 was out, I thought it may have rectified any such issues.
MacBook Pro (15-inch, Early 2011), 2 GHz Intel Core i7, 16GB RAM
DaVinci Resolve
Offline
User avatar

Uli Plank

  • Posts: 21281
  • Joined: Fri Feb 08, 2013 2:48 am
  • Location: Germany and Indonesia

Re: 15.2 & 15.2.1 fail to start on macOS

PostFri Dec 07, 2018 2:12 am

Which Mac? Which GPU?

Both versions work fine here.
No, an iGPU is not enough, and you can't use HEVC 10 bit 4:2:2 in the free version.

Studio 18.6.5, MacOS 13.6.5
MacBook M1 Pro, 16 GPU cores, 32 GB RAM and iPhone 15 Pro
Speed Editor, UltraStudio Monitor 3G, iMac 2017, eGPU
Offline

Pacific

  • Posts: 120
  • Joined: Tue May 08, 2018 9:45 pm
  • Real Name: Robert Wilde

Re: 15.2 & 15.2.1 fail to start on macOS

PostFri Dec 07, 2018 6:02 am

I'm on MacBook Pro 15" 2012 retina and never had a problem starting up.

I experienced the black frame issue as a bug in this version, but no beach balls, crashes, or startup problems.

Hope this helps to pin down the problem.

PS: Do you have Cuda enabled? I have turned off Cuda and enabled "OpenCL" This because there is NO valid cuda driver by NVidia for my MBP, so I turned it off.
DaVinci Resolve 18.6.5 Build 7
2020 27"iMac 4GB Vram 16GB RAM, i9 10-core processor, Mac OS Ventura,
Offline

Fortezza

  • Posts: 4
  • Joined: Thu Dec 06, 2018 8:50 am
  • Real Name: Mario Lombardo

Re: 15.2 & 15.2.1 fail to start on macOS

PostFri Dec 07, 2018 2:49 pm

Uli Plank wrote:Which Mac? Which GPU?

Both versions work fine here.


I have a MacBook Pro (15-inch, Early 2011) with built-in AMD Radeon HD 6490M and Intel HD Graphics 3000. I'm not sure which graphics card DR is picking up, but I hope it's the Radeon.
MacBook Pro (15-inch, Early 2011), 2 GHz Intel Core i7, 16GB RAM
DaVinci Resolve
Offline

Fortezza

  • Posts: 4
  • Joined: Thu Dec 06, 2018 8:50 am
  • Real Name: Mario Lombardo

Re: 15.2 & 15.2.1 fail to start on macOS

PostFri Dec 07, 2018 5:58 pm

Pacific wrote:I'm on MacBook Pro 15" 2012 retina and never had a problem starting up.

I experienced the black frame issue as a bug in this version, but no beach balls, crashes, or startup problems.

Hope this helps to pin down the problem.

PS: Do you have Cuda enabled? I have turned off Cuda and enabled "OpenCL" This because there is NO valid cuda driver by NVidia for my MBP, so I turned it off.


I was looking at the Apple crash log, and I did see a mention of CUDA along with some dynamic libraries, which I thought was strange. Here's a snippet toward the bottom of the crash log:

Code: Select all
                                VIRTUAL   REGION
REGION TYPE                        SIZE    COUNT (non-coalesced)
===========                     =======  =======
Activity Tracing                   256K        2
Dispatch continuations            16.0M        2
Kernel Alloc Once                    8K        2
MALLOC                            99.6M       24
MALLOC guard page                   32K        9
STACK GUARD                       56.0M        4
Stack                             9232K        4
VM_ALLOCATE                          4K        2
__DATA                            63.7M      357
__FONT_DATA                          4K        2
__LINKEDIT                       253.5M       61
__NV_CUDA                        124.2M        4
__TEXT                           794.4M      329
__UNICODE                          560K        2
mapped file                       25.5M        2
shared memory                      648K        7
===========                     =======  =======
TOTAL                              1.4G      797


I also found the following to "force" the higher-performance GPU [URL not allowed] gfxCardStatus, and I then tried to start DR then with no success.

The CUDA System Preference pane that I downloaded after experiencing these issues doesn't help remove any CUDA references as well. Could DR be hardcoded to reference CUDA exclusively? I'll sift through the actual DR logs now since I found the howto page. I'll post back with more progress.
MacBook Pro (15-inch, Early 2011), 2 GHz Intel Core i7, 16GB RAM
DaVinci Resolve
Offline

Pacific

  • Posts: 120
  • Joined: Tue May 08, 2018 9:45 pm
  • Real Name: Robert Wilde

Re: 15.2 & 15.2.1 fail to start on macOS

PostFri Dec 07, 2018 11:26 pm

Go to the DVR preferences , tab "memory and GPU" and set it to "OpenCL"

But make sure your MBP supports it. A pre-retina MBP is really outdated for this powerful software. My 2012 MBP is already borderline outdates - I'm just waiting for the new Mac Pro to be released to upgrade.
DaVinci Resolve 18.6.5 Build 7
2020 27"iMac 4GB Vram 16GB RAM, i9 10-core processor, Mac OS Ventura,
Offline

Fortezza

  • Posts: 4
  • Joined: Thu Dec 06, 2018 8:50 am
  • Real Name: Mario Lombardo

Re: 15.2 & 15.2.1 fail to start on macOS

PostSat Dec 08, 2018 12:45 am

Pacific wrote:Go to the DVR preferences , tab "memory and GPU" and set it to "OpenCL"

But make sure your MBP supports it. A pre-retina MBP is really outdated for this powerful software. My 2012 MBP is already borderline outdates - I'm just waiting for the new Mac Pro to be released to upgrade.

Alas, DVR (DaVinci Resolve?) simply does not start, so I'm left with a lonely Apple crash dialog. I am however in:
Code: Select all
/Library/Application\ Support/Blackmagic\ Design/DaVinci\ Resolve/logs

and I see
Code: Select all
davinci_resolve.log
with the following block of text toward the bottom:
Code: Select all
[0x7fff948b4380] | Undefined            | INFO  | 2018-12-08 00:21:58,146 | --------------------------------------------------------------------------------
[0x7fff948b4380] | Undefined            | INFO  | 2018-12-08 00:21:58,148 | Loaded log config from /Library/Preferences/Blackmagic Design/DaVinci Resolve/log-conf.xml
[0x7fff948b4380] | Undefined            | INFO  | 2018-12-08 00:21:58,148 | --------------------------------------------------------------------------------
[0x7fff948b4380] | Main                 | INFO  | 2018-12-08 00:21:58,152 | Running DaVinci Resolve v15.2.1.005 (macOS/Clang)
[0x7fff948b4380] | Main                 | INFO  | 2018-12-08 00:21:58,155 | Updating display GPU information...
[0x7fff948b4380] | Main                 | INFO  | 2018-12-08 00:21:58,155 | Detecting GPU properties
[0x7fff948b4380] | Main                 | INFO  | 2018-12-08 00:21:58,535 | Process to detect GPUs has finished
[0x7fff948b4380] | Main                 | INFO  | 2018-12-08 00:21:58,549 | Detected model 'MacBookPro8,2'
[0x7fff948b4380] | Main                 | INFO  | 2018-12-08 00:21:58,549 | Detected OS 'macOS 10.13.6 (17G4015)'
[0x7fff948b4380] | Main                 | INFO  | 2018-12-08 00:21:58,549 | Detected uptime 32155s
[0x7fff948b4380] | Main                 | INFO  | 2018-12-08 00:21:58,550 | Single GPU machine = Yes
[0x7fff948b4380] | Main                 | INFO  | 2018-12-08 00:21:58,552 | GPU Name = 'Intel HD Graphics 3000', Main display = 1
[0x7fff948b4380] | Main                 | INFO  | 2018-12-08 00:21:58,552 | GPU Name = 'AMD Radeon HD 6490M', Main display = 0
[0x7fff948b4380] | Main                 | INFO  | 2018-12-08 00:21:58,552 | 2 GPUs (excluding display GPU) found. Using OpenCL for processing.
[0x7fff948b4380] | Main                 | INFO  | 2018-12-08 00:21:58,552 | GLmap capable. GPUs: 1 discrete, 1 integrated, 0 external. Auto mapping, OpenCL processing, main display not on external GPU.
[0x7fff948b4380] | Main                 | INFO  | 2018-12-08 00:21:58,552 | Setting LsManager.3.NumGPUs = 1
[0x7fff948b4380] | Main                 | INFO  | 2018-12-08 00:21:58,552 | Setting LsManager.3.GPUMapping =  0
[0x7fff948b4380] | Main                 | INFO  | 2018-12-08 00:21:58,553 | Setting LsManager.3.GPUMappingEnable = 1
[0x7fff948b4380] | IO                   | INFO  | 2018-12-08 00:21:58,553 | RED InitializeSdk with library path at /Applications/DaVinci Resolve/DaVinci Resolve.app/Contents/Libraries
[0x7fff948b4380] | IO                   | INFO  | 2018-12-08 00:21:58,847 | R3DAPI 7.1.0-3YM06 (20180720 M64S) R3DSDK 7.1.0-3YM06 (20180720 M64D) RED CUDA 7.1.0-45494 (20180721) RED OPENCL 7.1.0-45494 (20180721) RED METAL 7.1.0-45891 (20181026) [/Applications/DaVinci Resolve/DaVinci Resolve.app/Contents/Libraries/] init is successful
[0x7fff948b4380] | Main                 | INFO  | 2018-12-08 00:21:58,853 | 0 RED rocket cards available
[0x7fff948b4380] | Main                 | INFO  | 2018-12-08 00:21:58,853 | Decklink model name: '', version: ''

Given this, it seems OpenCL is being used.

I think I've found the issue although I'm not sure where this leads from here. More investigation is needed. In the aforementioned directory, parsing through
Code: Select all
ResolveDebug.txt
I see:
Code: Select all
==========[CRASH DUMP]==========
Please send this to support:

#TIME Sat Dec  8 01:21:15 2018 - Uptime 00:00:00 (hh:mm:ss)
#PROGRAM_NAME DaVinci Resolve v15.2.1.005 (macOS/Clang)

0   Resolve                             0x00000001041f44f9 _ZN7DaVinci9Converter5Video5dpx10INS1_12dpx10conv_LEEE18VectorConvertTo16uEPKciPciii + 279449
1   Resolve                             0x00000001041f3a26 _ZN7DaVinci9Converter5Video5dpx10INS1_12dpx10conv_LEEE18VectorConvertTo16uEPKciPciii + 276678
2   libsystem_platform.dylib            0x00007fff5c49cf5a _sigtramp + 26
3   ???                                 0x0000000000000000 0x0 + 0
4   libsystem_c.dylib                   0x00007fff5c23a1ae abort + 127
5   libQt5Core.5.dylib                  0x000000011e7bcef9 _ZL16qt_message_fatal9QtMsgTypeRK18QMessageLogContextRK7QString + 9
6   libQt5Core.5.dylib                  0x000000011e7be84f _ZNK14QMessageLogger5fatalEPKcz + 239
7   libQt5Gui.5.dylib                   0x000000011edc73b6 _ZN22QGuiApplicationPrivate25createPlatformIntegrationEv + 6278
8   libQt5Gui.5.dylib                   0x000000011edc73db _ZN22QGuiApplicationPrivate21createEventDispatcherEv + 27
9   libQt5Core.5.dylib                  0x000000011e9d6411 _ZN16QCoreApplication4initEv + 113
10  libQt5Core.5.dylib                  0x000000011e9d6387 _ZN16QCoreApplicationC2ER23QCoreApplicationPrivate + 39
11  libQt5Gui.5.dylib                   0x000000011edc490e _ZN15QGuiApplicationC2ER22QGuiApplicationPrivate + 14
12  libQt5Widgets.5.dylib               0x000000011f7e2f0e _ZN12QApplicationC2ERiPPci + 206
13  Resolve                             0x00000001000367ee Resolve + 223214
14  Resolve                             0x000000010002ffc5 Resolve + 196549
15  Resolve                             0x0000000100054505 _ZN5boost2io6detail13call_put_lastIcNSt3__111char_traitsIcEEKNS3_12basic_stringIcS5_NS3_9allocatorIcEEEEEEvRNS3_13basic_ostreamIT_T0_EEPKv + 4533
16  libdyld.dylib                       0x00007fff5c18e015 start + 1
Signal Number = 6

================================
This application failed to start because it could not find or load the Qt platform plugin "cocoa".

Reinstalling the application may fix this problem.

The Cocoa API is quite vital to macOS, so now I'm going to attempt to satisfy this and determine why it happened. I have some guesses, but I'll refrain until I've exhausted some before I post back. Thanks for staying with me! ;)
MacBook Pro (15-inch, Early 2011), 2 GHz Intel Core i7, 16GB RAM
DaVinci Resolve

Return to DaVinci Resolve

Who is online

Users browsing this forum: 4EvrYng, Bing [Bot], carsonjones, govind, JRedstar, Omar Mohammad, peeceful, shikawkee, VMFXBV and 206 guests